Last few months Shabnam, & I were working on creating a podcast. Our podcast brings industry experts working in various Data practices. We focus on topics related to Big Data, Data Science, Database technologies, RDBMS. Many thanks to our colleagues & friends for their support in this initiative.

Here are links to our podcast:

Soundcloud -> https://soundcloud.com/data-podcast

iTunes -> https://itunes.apple.com/us/podcast/data-podcast/id1247751397?mt=2

Rick Krueger, director of PASSMN stopped by KFAI radio to discuss the interviews conducted by Dan English & Brian Larson of Superior Consulting. He talked about the significance of this event & the kind of impact it makes for fellow database professionals.

I have been lazy about blogging for a long long long time... I thought I'd get back into it again with an error message. Depending upon a project, I either get full-admin privilege or restricted privilege. Both options have merit, but, I prefer more flexibility in anything I do. This particular error message is very trivial. I'll not be breaking any ground by saying the solution is to grant proper permission. We often run into this kind of permission issues whenever dealing with database objects. It happens whenever the user lacks permission to utilize an object. How did I run into this error? I usually prefer storing ssis logging data in a table. One of these days, I'll get motivated to write my own custom solution. Until then I find the built-in logging mechanism sufficient. In most ssis projects, I had the privilege to utilize sp_ssis_addlogentry object. I didn't have to worry about setting that permission. When this issue arose I had to get help from our dba Jimit Mehta. He's a dba-super-hero for our team. As soon as he ran the statement below, my headache was gone. 

grant execute on sp_ssis_addlogentry to [domain_name\user_name]