Scheduled DTS Package

  • Hi All

    I have a peculiar problem. I am deconstructing an existing data warehouse, and in a SQL server Agent Job, DTSRun is called with a very long number after.

    It looks something like this:

    DTSRun /~Z0x435BDBD63242F36DEE43ED6C42A24A725CDCED0DF6DB5F23DC57E3DDC3D013D0BD94E1551CB57832A154FD50DEE8B283E8B0F2C031798A80AF839E4612C7674C9F0D69B273CBB6BF3226FF001FD247EA9BEFE5ACC107ED853665FDF0AB47A88C238F79F5B6A034CD7EC2AA4DA642A577D03AA9230614A09342A590916EDD42D96DEEA7DDEB7581AC513164EC5C7763D5CC07DFE1D7EA1B0FD9534ED0F777B576C22488B2BF56B042B4BD846988E21D0A8A9D59E90090A5969591B4E6AD035E5831A11D

    This is not the normal Package ID. I neet do trace this long number back to the package for debugging purposes. Does nyone know how to do this ?

    Thank you

    Frik


    Best Regards,

    Frik Venter

  • Yes, If you use the DTSRUNUI.EXE then it will produce an encrypted string that says what the package is, who the running user is, their password and various other pieces of information.

    It is this that you see with your ~Z switch.

  • Is there any way of decripting this string to see which DTS Package it represents ?

    Frik


    Best Regards,

    Frik Venter

  • If you Run the package then

    select top 10 *

    from msdb.dbo.sysdtspackagelog

    order by endtime desc

    You should see all recent logged packages that have run.

  • Great stuff

    This works.

    Thanks !


    Best Regards,

    Frik Venter

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

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