Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Using SQL Server 2005 (and 2008)

With a DTS package, I can open it, and it lists the date that the package was last modified. I have some SSIS packages, and I need to know if they have been modified since our last release. Is there any way to tell when they were last modified?

If I right-click, the only option that even looks promising is "Reports", but the only option there is a general report that has the package creation date and some versioning information. I already know that the programmer didn't change any of the version defaults, so there is no useful information there.

I want the last modified date, or last imported date, or something to let me know if I need to worry about some of these being modified since our last release.

Edit: The file is stored in MSDB.

share|improve this question
up vote 3 down vote accepted

If the packages are stored in MSDB then no, the only date/time stamp is the creation date. Modified date is not tracked. You would need to delete the package prior to redeploying in order to track a modified date, which is essentially just forcing the create date to be your redeploy date.

In SQL 2005, the metadata for packages stored in MSDB is stored in msdb.dbo.sysdtspackages and msdb.dbo.sysdtspackages90 so you can run a SELECT on one of those tables to see your packages. For SQL 2008 and beyond, the table name is sysssispackages.

SELECT * from msdb.dbo.sysdtspackages90 WHERE name='mypackagename'

If your package location on the server is File System then you can get the modified date on the package file via Windows Explorer (or whatever file system tool you want to use). The path for SQL 2005 is [install drive]:\Program Files\Microsoft SQL Server\90\DTS\Packages\. Replace the 90 with 100 for SQL 2008, or 110 for SQL 2012.

Otherwise, I think your best bet would be to make sure security on your production server is adequate such that only those who should be deploying packages are, and then to track your publishing dates in your dev environment (source control, whatever). Doesn't really do much to ensure that production isn't changing without knowing about it, though....

share|improve this answer
It's in MSDB. :( – thursdaysgeek Jan 5 '10 at 18:10
It sounds like we need to add a date to the meta data, each time we check it in. Or something! – thursdaysgeek Jan 6 '10 at 0:28

Here's a great post about how to retrieve information from an SSIS package. It's helped me to find information I've needed in the past and it may be of use to you:

share|improve this answer
This is useful to check metadata on dtsx files themselves, but the original question was asking about packages stored within MSDB. – anon Jun 27 '14 at 13:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.