Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
efelito
Constraint Violating Yak Guru
478 Posts |
 Posted - 2002-03-22 : 11:12:04
|
Any one know how to determine the name of the package that DTSRun is executing? I've been tasked with figuring out what a set of jobs do on a server that no one has any info on. There are DTS packages being run using the DTSRun utility like so. quote:
DTSRun /~S 0x79890F8EE93F2E48D2A80B4A56FAC469EAB78E3E4E39BE85 /~N 0x57E89014C2EE41E2DB33A15D15FE593EBA603DB9C145E8F77191B65AF4D846E8721A7550A4C02ABB /E
They didn't name the job step any thing like the package name, so I need to figure out the name of the package that is running from this line. Dazed and Confused.Jeff BanschbachConsultant, MCDBA |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-03-22 : 11:15:47
|
| Take a look in the sysdtspackages table in msdb Jeff. There's a couple of GUID columns, one of them will match the package GUID and another has the version GUID. |
 |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-03-22 : 11:29:20
|
| I checked those out before but couldn't figure out how they related to the /~N part of the DTS package. Do those GUID's need to be concatenated, converted to hex and compared to the switch in DTSRun?Jeff BanschbachConsultant, MCDBA |
|
|
|
yakoo
Constraint Violating Yak Guru
312 Posts |
Posted - 2002-03-22 : 11:43:55
|
| Im not really sure if you will be able to compare themthe ~N option with DTSRun endicates that the following values are the hexadecimal text representation of the ENCRYPTED value of the package name. |
|
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-03-22 : 11:52:07
|
| I just found that little tid bit in BOL too. That's not good. I'll keep hacking at it, but if any one has any idea how to trace this back I'm listening.The part that sucks is that no one intended to encrypt this stuff. I'm sure they just right clicked on the package and said schedule package, then copied the dtsrun lines into their other jobs. It worked and they didn't think about it again.Creating tomorrow's legacy systems today... one line of code at a time.Jeff BanschbachConsultant, MCDBA |
|
|
|
|
|
|
DTSRun Naming Problem