Copying Scheduled Jobs to Another Server

Question

Post reply

Copying Scheduled Jobs to Another Server

Helen-84411

Hall of Fame

Points: 3320
More actions
June 29, 2005 at 5:03 am

#114342

Hi,
How do I copy scheduled jobs to another server. I know that I can generate the script and execute the same on another server. Do we have any other means like copying entries from msdb...
Any help

Helen
--------------------------------
Are you a born again. He is Jehova Jirah unto me

Viewing 5 posts - 1 through 4 (of 4 total)

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

Mohammad Sufian Ten Centuries Points: 1292 More actions · Answer 1

Hi,

Always finding diffrent ways to do.

The one i know is restore the system databases on other server.

or use DTS services to tranfer jobs.

need more help.

sufian

Mohammad Sufian Ten Centuries Points: 1292 More actions · Answer 2

Hi,

As i mentioned before u can use DTS Package to transfer ur jobs from one server to other.

DTS services--->new package ---> select tranfer job task.--->property window will diplay to u .

(i) give the server name from where u want to tranfer jobs(source server)

(ii) give server name or ipaddress u want to transfer jobs(destination server)

(iii) select the jobs to tranfer save it and execute it

from'

sufian

dbuchan SSCrazy Points: 2328 More actions · Answer 3

Or you can do SAVE AS and pick the other server.

OK for a few packages at a a time.

DB

The systems fine with no users loggged in. Can we keep it that way ?br>

Jeff Gray SSChampion Points: 10667 More actions · Answer 4

I think the *easiest* way is to script the jobs and run the script on the target server.

Now there is a gotcha with this method. If any of your job steps use T-SQL containing BATCH separators (GO), then QA will strictly interpret the GO as a batch separator during the creation of the jobs. This will result in jobs that do not get created. QA doesn't know the difference between the GO in a multi-batch T-SQL step and the ones in between the batches that create the steps....

The workaround is to tell EM to use a different batch separator when you create the script. There is an input field in the EM script UI for just that. I normally use

--DONTGO--

Then, when I want to create the jobs on the target server, I need to tell QA that I want to use --DONTGO-- as the batch separator and all works fine. That is in Tools,Options,Connections tab.

Now if I could just remember to set it back to GO when I'm done.

I don't know if you're looking for an easier way to do this because you've run into problems, so I provide this in case it makes things easier. HTH

jg