June 27, 2005 at 8:23 am
Hi all,
I have to copy nearly 35 jobs from server1 to server2.Do I have to do them manually(creating same jobs on server2) or is there some quicker way to do this.
I tried scripting them but it won't let you to copy the script.
Please help.
Thanks.
June 27, 2005 at 8:37 am
How do you mean "it won't let you copy the script?" I ask because, that's how I've migrated SQL Agent jobs in the past. Export them out to a script and then run that script on the next server.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
June 27, 2005 at 8:48 am
Ditto here. Script them, do a search and replace if needed for servername, and run the script on the nwe server.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
June 27, 2005 at 9:01 am
Thanks a lot.Ya it was simple.But When I did it before it was scripting in some other format which I could not copy..
Now when I do it ,
It gives a message while creating the script.
"A job command contains the TSQL Batch separator 'GO' .This may cause problems while running the script generated by this dialog.Use a different TSL Batch separator while executing the gnerated script"
Does that mean that I have to remove 'GO" from the script before running it.
Thanks.
June 28, 2005 at 12:42 am
One doubt please..
why cant you use the msdb database for your requirement.
sysjobsteps has all the scripts which were used to create the jobs?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply