>Check the tables in the MSDB database on your SQL Server.
>On my SQL 7 server:
>Local Packages are in: sysdtspackages and your ID code maps to an ID field
>I'm not certain where meta data services packages are stored. they may be there
Meta Data packages are stored in MSDB, but there is no one table like
sysdtspackages. It has also changed between 7.0 and 2000. Don't go
there, use the object model.
>And Duh... I just noticed, if you open each package and bring up it's
>properties, you get the name plus the Package ID. So that may be the brute
>force method of finding it out.
>> I've inherited a legacy system with a package that runs every day.
>> SQL Agent lists the job step as
>> How can I decipher what package this corresponds to? Someone has renamed
>> all the packages so I can't use that info from the Job Step.
If you look in Books Online for DTSRUN, /~Z or /Z as it is also
(incorrectly) documented means that this is a single encrypted parameter
that contains all the information such as serevr, connection details,
and package details used to schedule execute that package.
You cannot decrypt this. Normally both the job name and step name are
the same as the package name. If the package has been renamed I guess
the jobs will fail as it can no longer find the package.