May 7, 2015 at 3:57 am
Just a simple question,with no being the most likely answer.
So scenario, a high support call comes in,the records in a Business critical table are off.
Trace reveals a delete statement being executed by a separate job then the daily synch one.
It took me a while to trace the exact job down,but I recognise it as being one I created long ago (> 1 year)
when my access to the business sql environment was limited and I had to use an external workstation.
Downloaded the package from msdb as the solution is no longer available & immediately see some changes that are not from my 'hand'.
Corrected the package & redeployed,being hopefull the would have solved the issue.
Now the question is;can I somehow see a history of every time a package was reuploaded.
May 7, 2015 at 6:09 am
Afraid not, the only thing I could find in my testing is that a table in msdb keeps up with the version build but it does not give you any date on the last time the package was uploaded to the msdb database. The only thing I saw change was the verbuild value in sysssispackages.
You can however do this in SSIS 2012 when you are using the project level deployment to the SSISDB catalog. You can configure the number of versions that are kept and actually setup SQL Server Audit against the database and such to monitor it in more detail.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply