dbTalk Databases Forums  

DTS simple problem?

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS simple problem? in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
ChiWhiteSox
 
Posts: n/a

Default DTS simple problem? - 03-13-2006 , 04:05 PM






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..

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: DTS simple problem? - 03-13-2006 , 04:12 PM






Hello ChiWhiteSox,

If when you installed SQL Server 2K5 you installed the 2K runtime then you
still have DTSRun. You can use that in a job step just like you used to do.


Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Quote:
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..




Reply With Quote
  #3  
Old   
ChiWhiteSox
 
Posts: n/a

Default RE: DTS simple problem? - 03-13-2006 , 05:46 PM



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:

Quote:
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..

Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default RE: DTS simple problem? - 03-13-2006 , 06:09 PM



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

Quote:
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..




Reply With Quote
  #5  
Old   
ChiWhiteSox
 
Posts: n/a

Default RE: DTS simple problem? - 03-14-2006 , 10:40 AM



thanks so much allan! it worked!!

God Bless

"Allan Mitchell" wrote:

Quote:
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..





Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.