November 5, 2008 at 9:45 pm
This is on SQL Server 2000. We made a copy of our production server for development environment. The problem we’re having is with SQL Server Jobs. The jobs are updating the production server instead of the newly created server. The jobs are running DTS packages. I can run the DTS package and it updates the correct server, but when I create a schedule a job from DTS it runs on the production server.
Thanks in advance.
November 5, 2008 at 10:18 pm
gator88 (11/5/2008)
This is on SQL Server 2000. We made a copy of our production server for development environment. The problem we’re having is with SQL Server Jobs. The jobs are updating the production server instead of the newly created server. The jobs are running DTS packages. I can run the DTS package and it updates the correct server, but when I create a schedule a job from DTS it runs on the production server.Thanks in advance.
create the jobs on the desired server or if not possible change the execution path of the jobs by prefixing the server path
kshitij kumar
kshitij@krayknot.com
www.krayknot.com
November 6, 2008 at 8:45 am
Even when I recreate the jobs they run on the old server. I can run the DTS manually on the new server and they work fine.
November 7, 2008 at 5:41 am
Check the connections within the dts package - a lot of times they are "hard coded" to a specific server. Also check the job step - /S "(local)" indicate the local server, but I've had instances when a job on one server was set to run on a different server. hih
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply