Post reply

JOBS

  • January 16, 2007 at 10:34 am

    #68256

    I have SQL Agent Jobs which runs 4 DTS,

    I want to add another step which contains DTS, how to add that new DTS in SQL agent in the existing job.

    Nita

  • January 16, 2007 at 10:40 am

    #683551

    Open the job property;

    Goto steps tab;

    Click New button;

    ...

    You would miss it.

  • January 16, 2007 at 10:52 am

    #683557

    I already have DTS, which need to be replace with this new one. How to get DTS??

     

    Nita

  • January 16, 2007 at 12:54 pm

    #683592

    If you are asking how to execute a dts package from a SQL job you use the DTSRUN utility.  Information on this can be found in Books Online. 

    Francis

  • January 17, 2007 at 7:03 am

    #683711

    I have one SQL Agent Job which contain 4 steps.

    step number 3, I want to replace DTS package

    DTSRun /~Z0x746C6215E6EBA199A6637D129B20672C845F62849F98141FC14858C32D7F0A313BB17632AD81D25B5CCE62058B9115ECF504B8E7DF27F92CA9AF6FF5F389F62D78BF6543026EE0FDCD6A212C577BBFD49B65260AF45D828B48E71BD7AC1C450B87C760D1961ED9B63F2CAC7124DDF882D5038D

    with the newly created DTS called Import Package.

    Nita

     

  • January 17, 2007 at 7:09 am

    #683712

    Right click on the new package, schedule, OK.

    Then open the newly created job, cut / paste the dtsrun line from the new job to the current one. Save and test.

  • January 17, 2007 at 7:16 am

    #683714

    Thanks,

    But I cannot do that because of SOX related. It's there any way from MSDB datawere where I can get this whole path. I tried but was helpless.

    Nita

  • January 17, 2007 at 7:29 am

    #683720

    You got me there.   I don't see it anywhere in the dts itself... Saying that I didn't scan the system tables.  Maybe it would be faster to just ask access to implement the thing... I'm sure there must be a way for someone to have access to the production server !?!

  • January 17, 2007 at 7:44 am

    #683729

    I know you can change it, but how?

  • January 17, 2007 at 8:12 am

    #683743

    Why is SOX preventing you from editing the job? 

    Replace the line

    DTSRun /~Z0x746C6215E6EBA199A6637D129B20672C845F62849F98141FC14858C32D7F0A313BB17632AD81D25B5CCE62058B9115ECF504B8E7DF27F92CA9AF6FF5F389F62D78BF6543026EE0FDCD6A212C577BBFD49B65260AF45D828B48E71BD7AC1C450B87C760D1961ED9B63F2CAC7124DDF882D5038D

    with

    DTSRun /S "(local)" /N "Import Package" /E

    I can't see any difference in creating the DTSRUN job manually or having SQL create it for you by right clicking on the package in Enterprise Manager and selecting schedule.  EM encrypts the command line. However this no longer provide protection as there is at least one public tool that allows the decryption of the cipher text. There is some risk mitigation in the restriction that only members of the sysadmin role or job owners can see the details of a given job.

    If you really must encrypt the line use the /!X switch.

    I prefer the unencrypted line as its more clear for maintenance and I can replace the package without having to redo the scheduled job since the encrypted line refers to the package GUID rather than the name.  (and none of my other maintenance jobs are encrypted) If I replace the package from a copy developed on the test server the GUID changes, so now the EM created DTS Run string is no longer valid. On the other hand my DTSRun statement is still valid. 

     

    Francis

  • January 17, 2007 at 2:44 pm

    #683864

    I was going to reply similar to fhanlon.  We code our DTS packages in jobs like this:

    DTSRun /S SERVER_NAME_HERE /E /N "DTS NAME HERE"

Viewing 11 posts - 1 through 10 (of 10 total)

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