SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


When was an SSIS package imported?


When was an SSIS package imported?

Author
Message
caddywonkus
caddywonkus
Valued Member
Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)Valued Member (73 reputation)

Group: General Forum Members
Points: 73 Visits: 564
Scenario: an SSIS package deployed to msdb is accidentally overwritten. The new package was "supposed" to be deployed to a QA server but may have been inadvertently deployed to production. Of course, database objects it depends on were not deployed there, so the package fails miserably as it should.

Short of exporting the existing package and comparing it to its older-version self... is there anything in the msdb database that logs the event of having imported the package?

I'm trying to confirm - or deny - the suspicion. Unfortunately it would have been deployed via a BAT file calling DTUTIL, and the author of that file didn't include anything to log what server was fed into it. No, I don't like it either but keep in mind I'm in a large company with a lot of servers, and two DBA's. We're well divided - the DBA's handle ALL deployments to QA and production, but the method of deployment isn't always in our hands. I've already advised the development team involved to not send us these batch files, we can handle directly deploying the packages ourselves. And I already have plans for a central, file-based SSIS server.

But for now, we have what we have, and I just want to find out for sure if someone accidentally deployed the package to the wrong server. If it were a procedure I could simply query sys.objects and check the create_date or modify_date columns. I'm hoping there's something similar in msdb for a server-stored package. The sysssislog table doesn't appear to have import events logged, and the create_date column in sysssispackages reflects the date the package was created, not imported; and I can't seem to find any other columns in any other tables to show it empirically, either.
Koen Verbeeck
Koen Verbeeck
One Orange Chip
One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)One Orange Chip (27K reputation)

Group: General Forum Members
Points: 27111 Visits: 13268
I'm afraid such data is not available. As you found out yourself already, only the creation datetime is stored.

You could add your own logging columns using defaults and triggers, but then you would be messing with system tables.


How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?
My blog at SQLKover.

MCSE Business Intelligence - Microsoft Data Platform MVP
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search