March 16, 2011 at 7:54 am
I've got a SQL 2000 Db that I inherited that has had many fingers on it over sever years. There are several DTS packages and jobs that schedule them. One package doesn't exist anymore and was named Process_downloads. It was tweaked and now one named Process_downloads_2 is there. In the job scheduler, there is a job with several steps, step one being to run this package. OK, it's obviously running the right package, but the step of the job is like this:
Step Name: Process_downloads
Type: Operating system command
command: DTSRun/~Z0xCDD5AFAC04E9E4204E602275285AE3C70DE647470CA72C4E51DCB895D6B25E5FFA94870A051FEDD281F4BF984CEA909
so, my question is - Where does that ID number come from? How can I check to make sure that DTSRun is pointing to the correct package?
I can create new jobs that use that same package, but each time I do the GUID generated for DTSRun is different? What's up with that?
Thanks
K
March 16, 2011 at 9:58 am
That "ID" is a crypted string that contains all the information on package name and version, server name and credentials to log in to the server that holds the DTS package.
In order to ensure you're running the right DTS, schedule the one you want to run in a new job, copy that string and paste it into your job step.
Hope this helps
Gianluca
-- Gianluca Sartori
March 16, 2011 at 10:14 am
that's the part that's really confusing me. I can create a new job scheduling a package to run. Then do it again using the same package but the string is different each time I do that. I did this 3-4 times and the string is different each time.
I guess part 2 of my question is is there anyway to visually check what DTS package a job points to?
oh, and THANKS for replying. I really like this forum!
March 16, 2011 at 10:27 am
Uripedes Pants (3/16/2011)
that's the part that's really confusing me. I can create a new job scheduling a package to run. Then do it again using the same package but the string is different each time I do that. I did this 3-4 times and the string is different each time.
I suppose that the same settings can be encrypted with a different resulting string. I would have to look it up.
I guess part 2 of my question is is there anyway to visually check what DTS package a job points to?
None that I'm aware of, sorry.
-- Gianluca Sartori
March 16, 2011 at 10:40 am
OK, thanks. I'd be happy to look it up myself, but don't really know where to start to look.
The not being able to identify the DTS package that a job runs seems like a heafty limitation to me. We're in the process of moving/upgrading a bunch of 2000 servers to 2008r2 and it would be pretty handy - but I guess it's WAY to late to complain to MS about SQL2000 ;o)
just had a thought....
OK, I just had SQL server script out the job and the DTS package is only referred to by ID num in that script also.
well, thanks for replying!
March 16, 2011 at 10:51 am
OK, found it.
Just add the /!Y parameter to DTSrun.exe and it should display the original parameters.
-- Gianluca Sartori
March 16, 2011 at 11:03 am
COOL! Is that in BOL? someplace where I can look to check exact syntax and usage?
never mind....I just googled and found several useful pages. Seems MS encrypted the command line on purpose for "security" reasons.
Thanks for pointing me in the right direction.
March 17, 2011 at 9:01 am
To decrypt a DTSRUN command as used in a job step, copy the command to a cmd prompt, append /!X /!C to the end, and run it.
The !X argument blocks execution of the package and the !C argument copies the unencrypted command to the Windows clipboard.
Just open Notepad and paste to see the unencrypted command.
Example:
DTSRun /~Z0x5F473BFAEEC0EE48EAF6121A88792F925A32FAF162A18E19FB06C5246A4CA2785EE38A17F0A6101C17B16C8F336C65EBF60B0E624C1E9B83 /!X /!C
Greg
March 17, 2011 at 9:14 am
Greg -
thanks for that. I think the /!Y switch previously mentioned is actually to take it the other way - CREATE the encrypted string from parameterized DTSRun command.
It was kind o academic at this point, but the /!X /!C does decrypt the string and allows one to see exactly the package that is called.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply