![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi We just upgraded from sql 2k to 2k5. I was able to import all dts jobs successfully on the 2k5 server. How do i no run those new;y imported jobs on the 2k5 server? when I right click on the main dts job, I dont see any execute job or even schedule the job? So what i did, I migrated the dts job from 2k5 to ssis. Logged in thru Integ services and was able to run the migrated job. There's gotta be a way to run the DTS jobs without migrating them, am i right? so now if i wanna sched this migrated job, I go to the comand line properties of the migrated job and copy the command line and paste on when i create the new job on sql server agent. Am i doing this the wrong way? Thanks for any thoughts.. |
#3
| |||
| |||
|
|
Hi We just upgraded from sql 2k to 2k5. I was able to import all dts jobs successfully on the 2k5 server. How do i no run those new;y imported jobs on the 2k5 server? when I right click on the main dts job, I dont see any execute job or even schedule the job? So what i did, I migrated the dts job from 2k5 to ssis. Logged in thru Integ services and was able to run the migrated job. There's gotta be a way to run the DTS jobs without migrating them, am i right? so now if i wanna sched this migrated job, I go to the comand line properties of the migrated job and copy the command line and paste on when i create the new job on sql server agent. Am i doing this the wrong way? Thanks for any thoughts.. |
#4
| |||
| |||
|
|
oh ok, cool so DTSRun packagename will work... how do i generate the parameters for that DTS package name, i understand its a hex code right ? so i can run this normally as a TSQL code? thanks! "ChiWhiteSox" wrote: Hi We just upgraded from sql 2k to 2k5. I was able to import all dts jobs successfully on the 2k5 server. How do i no run those new;y imported jobs on the 2k5 server? when I right click on the main dts job, I dont see any execute job or even schedule the job? So what i did, I migrated the dts job from 2k5 to ssis. Logged in thru Integ services and was able to run the migrated job. There's gotta be a way to run the DTS jobs without migrating them, am i right? so now if i wanna sched this migrated job, I go to the comand line properties of the migrated job and copy the command line and paste on when i create the new job on sql server agent. Am i doing this the wrong way? Thanks for any thoughts.. |
#5
| |||
| |||
|
|
Hello ChiWhiteSox, The HEX you saw in 2K was just to encryt stuff. It as not "Required" For the switches have a look at this article http://www.sqldts.com/default.aspx?301 Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com oh ok, cool so DTSRun packagename will work... how do i generate the parameters for that DTS package name, i understand its a hex code right ? so i can run this normally as a TSQL code? thanks! "ChiWhiteSox" wrote: Hi We just upgraded from sql 2k to 2k5. I was able to import all dts jobs successfully on the 2k5 server. How do i no run those new;y imported jobs on the 2k5 server? when I right click on the main dts job, I dont see any execute job or even schedule the job? So what i did, I migrated the dts job from 2k5 to ssis. Logged in thru Integ services and was able to run the migrated job. There's gotta be a way to run the DTS jobs without migrating them, am i right? so now if i wanna sched this migrated job, I go to the comand line properties of the migrated job and copy the command line and paste on when i create the new job on sql server agent. Am i doing this the wrong way? Thanks for any thoughts.. |
![]() |
| Thread Tools | |
| Display Modes | |
| |