Saving a DTS package always creates new version?

Question

Saving a DTS package always creates new version?

Ray Cacciatore

Ten Centuries

Points: 1260
More actions
February 11, 2010 at 2:07 pm

#219101

How do I know which version of a DTS package is running on my server when it contains several versions? When I open a package, a dialog appears with a little plus sign nest to the name, when I click the plus sign I see the different versions.
1) How do I know which version is running.
2) How can I make it run an older version without deleting the newer version.
For your info:
The packages are saved as SQL Server packages, not files. I'm running the DTS add-on in SQL Server 2005 so the packages appear under the Management->Legacy->Data Transformation Services node.
Thanks

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Greg Charles SSC-Forever Points: 45403 More actions · Answer 1

You can find the version guid values by querying msdb.dbo.sysdtspackages. Once you know that, you can see which version is used in the DTSRUN command and you can specify which version to execute in the DTSRUN command by including the V argument and the package version guid.

Greg

Ray Cacciatore Ten Centuries Points: 1260 More actions · Answer 2

Question #1:

I noticed there is a sysdtspackages table and a sysdtspackages90 table. I'm currently running my DTS packages on SQL Server 2005. We installed the DTS components add-on. So which table should I be looking in?

Question #2:

One of my packages calls a child package. But I keep getting an error saying that the parent package is expecting a child package with a specific GUID. I can't remember the exact error, but somewhere along the lines of "The package with ID.VersionID {A234-5435435-345345-fe4} expected does not exist.". In other words, it looks like the parent remembers the GUID of the child package and expects it to be there every time. It looks like my DBA made a modification to the child package, so it crashes. When I look in the sysdtspacakges table, the GUID isn't even there.

Thanks.

Greg Charles SSC-Forever Points: 45403 More actions · Answer 3

#1 DTS packages are stored in sysdtspackages. SSIS packages are stored in sysdtspackages90.

#2 Look at the properties of the Execute Package Task in the parent package. It's possible that it was originally set up to use a specific version of the child package then deleted that version. Click on the elipse next to the package name box and select the name of the child package without expanding the versions to make it use the latest version.

Greg