Checking Management Jobs - running DTS packages.

Question

Post reply

Checking Management Jobs - running DTS packages.

Torben Søeborg-313972

Grasshopper

Points: 14
More actions
March 26, 2006 at 10:37 pm

#116664

Hi there.

I´m currently consolidating several SQL2000 servers, and I stumbled over a server having multiple Management jobs scheduled.
>>
>> When i check the steps, I see this string:
>>
>> DTSRun /~Z0x121AD1C1C5023EE53ABCFE5DF22FDD166C81A8763A147739EEF7EABEBC0F79A516F316482F5D0C592216E08EF1093F41D76F23B6CF8D41E29D07EE4B8428EAF44098B2E239C178F29533D47F2FC1D96658D6E24A719B7997580DFE69C133DAB6829DDF00E2C141583515FFE54C2EC00D188EC6FA8E0BF2F08B071556CBE2B1EDAF6F427019182B227268A310CA567ED95691D7D9BA0DDF1274DE99
>>
>> I did check Local Pacages, and yes, multiple DTS packages is present. But how do I the easiest check which DTS package the Management job is running?
>
>-- Torben.

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

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

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

There's no direct way to decrypt the DTSRUN parameters, but try this:

1.Run the package, either by starting the job or copying the DTSRUN line to a command prompt.

2.Then run this in QA:

select top 10 *

from msdb.dbo.sysdtspackagelog

order by endtime desc

You'll see the most recently run package.

Greg

Torben Søeborg-313972 Grasshopper Points: 14 More actions · Answer 2

Hi Greg.

Thanks for the fast reply - I´ll try that, and hope that I´m not executing "Drop Tables" or similiar

Thank God for Backups ..

steve block SSCertifiable Points: 7698 More actions · Answer 3

I have some jobs that use dtsrun in multiple steps. I created them by going selecting "Schedule Package", which creates a job with the same name as the Package. I then go copy the DTSRUN command from the job that was created to a step in the job that has the multiple steps and disable the job created by "Schedule Package". There may be old disabled jobs that contain the DTSRUN to compare the step's DTSRUN to.

Also, I assign a step name that ties the DTSRUN back to the original dts package. If the person(s) that created this job did either one of these things (left the job create from the package and just disable it) or named their steps in a meaningful way, you may be able to figure them out.

Steve