Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SSIS and Import/Export (2005)
 DTS to SSIS package

Author  Topic 

GMANAFIP
Starting Member

13 Posts

Posted - 2008-09-21 : 23:53:32
I have a DTS job in SQL Server 2K that I brought over in SQL Server 2K5 under legacy and I can't seem to schedule it write. If I run the package manually it works fine but if I schedule it it does not seem to work - no error. I don't know if I using DTSRUN with the operating system command (cmd exec) write or should I be using some other command. It is what the schedule job code used in SQL Server 2K with all the appropriate switches when I brought it over to SQL Server 2005. Any help you can give would be great.

Thanks

visakh16
Very Important crosS Applying yaK Herder

52326 Posts

Posted - 2008-09-22 : 05:00:19
whats the job basically doing?
Go to Top of Page

GMANAFIP
Starting Member

13 Posts

Posted - 2008-09-22 : 07:00:49
The job take data from one database on one server to another databse on another server.

The code is: DTSRun /~Z0x1B4BD87B185961EA8B0161D48BD2125FFEC3FDF95F8B72D118AF5673E03DEF01DA2C75990D07884CF076A02C03DB90F3C4C626F1BC6B28DB4237C4BDB22E3AEC4AF8FF6115284DE3A97DF9710ABBE6A21663A30E18811AD2CD87AED5CD162E6A6E7C94
Its' weird because if you look at the job status it says it was completed successfully but I can clearly see is did not do the job. Any ideas?
Go to Top of Page

saurabhsrivastava
Posting Yak Master

216 Posts

Posted - 2008-09-29 : 21:18:16
Use DTrun.exe -Server -PackageName -User -Password command instead of using encrypted code. I had this problem solved by using above method
Go to Top of Page
   

- Advertisement -