Viewing 15 posts - 16 through 30 (of 186 total)
July 12, 2018 at 8:11 am
July 11, 2018 at 3:09 pm
July 11, 2018 at 3:06 pm
After verifying all the settings, I've seen this happen at times and I think...
April 27, 2018 at 10:26 am
Figured this out and here is the solution .It may help somebody some day.
declare @xmlstr xml
set @xmlstr = ---all my XM query here...
December 1, 2017 at 7:43 am
August 9, 2017 at 12:58 pm
August 4, 2017 at 3:34 pm
June 22, 2017 at 7:37 am
June 15, 2017 at 2:34 pm
Steve Jones - SSC Editor - Thursday, June 15, 2017 11:11 AMHow does it call the SSIS package?
Through the VB code.
June 15, 2017 at 12:44 pm
Sorry this is not a sql job . It's a windows job running through task scheduler that calls a SSIS in the VB code. The job is run by user1...
June 15, 2017 at 10:27 am
The issue is resolved. Phew!
I had copied the master key to a random folder and realized that the SQL Server service account did not have permission on this...
April 28, 2017 at 7:45 am
April 25, 2017 at 11:14 am
I also added NT SERVICE\MSSQLSERVER to the sysadmin role and it worked , I am not getting the previous permission to execute error now.
April 25, 2017 at 11:10 am
Viewing 15 posts - 16 through 30 (of 186 total)