How to see the real command in DTSrun/~Z

  • Does someone knows, how can i see the real command in DTSrun/~Z.

    I have de follow command:

     

    DTSRun /~Z0xFCE4267FFC0BB92179B34B61481850E001AC8DB02B98E864184BC2D7CB0AB923658C6A9E97DEDD099FE5A8758A89630BBECACE23AD5C563801F5B6585E614E2EF78C125A6BD5F97CE11D07D1438833EA9ACB2380183382EEADFF29924424EAC9F555CFC81A2B02D2911FCCAE176464F16A2D40797E62EAA5BADDBA4B0591804ACA8F861D23E44215510D07

     

     

    I need to see, why the job that run this command is taking a long time to run...

     

     

     

    Regards,

     

    Felipe Venancio

  • If you go to DTSRUNUI utility,

    There is a option to see the DTSRUN command for the package in both text format and encrypted format.

    Hope this help!!

     

     

  • When scheduling DTS packages by right-clicking on the package name and then selecting "Schedule Package", the job is created with the DTSRun string automatically encrypted.  But, the job is saved with the same name as the DTS package that was scheduled.

    However, if the job was created by using the DTSRUNUI.exe utility, and the encryption option was used when generating the DTSRun string, then there is no way that I know of to decipher what package is being run.

    Hope this helps.

  • Run your cmd with /!X /!C

     

    DTSRun /~Z0xFCE4267FFC0BB... /!X /!C

     

    This will put the decrypted cmd string into clipboard buffer, paste it into your notepad.

     

    In order for this to work you'll need to

    1. Have connection to your SQL server cause it will try to connect to your SQL and

    login using whatever login info in this encrypted string, if it use /E then you will need to have

    right using windows authentication connect to your SQL.

     

    2. You'll need to have the target dts package on your server

     

    If these 2 conditions not met, you'll

    need a program name dtsrundec - someone from Russia create it to decrypt it.

    Find it on the net, I remember you'll need Visual C++ compiler to create the .EXE file.

     

    Good Luck!

     

     

    James Pua

    MCSE, MCSD, MCT

     

     

     

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

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