Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a SQL Server Agent job comprised of 10 steps and each step has many parameters defined. Now I need another job almost exactly the same, but with a few differences. Since "copy / paste" isn't an option for jobs, I'm looking for suggestions on what would be the best way to create a new job based on the first.

Edit: I just noticed that I can right-click and "Script Job As". I suppose one option would be to do just that and edit the script for my changes. I'm still curious as to if there are any other (better?) options as well.

share|improve this question
up vote 8 down vote accepted

I don't think there is a better option than scripting your job. You can modify the script as required and reapply it to any number of SQL instances (always backup your system databases before apply scripts).

share|improve this answer
This seems to be the best way to go when copying jobs in the same instance. – Chris_K May 21 '09 at 23:59
Be aware that unless you remove the @schedule_uid then the new job will be created using the same schedule as the original, i.e. changes to the schedule in the copied job will also change the schedule in the original job. See this question on Database Administrators:… – flash Sep 16 '14 at 13:51

You may find the SQL Server Integration Services Task, Copy Job to be of use.

share|improve this answer
I had looked at that, but it doesn't seem to help me copy a task on the same instance. I guess I could copy from instance a to instance b, rename and modify and then copy back but with my ADD issues I'm sure to lose track of what I'm doing halfway through! :-) – Chris_K May 21 '09 at 14:49

I used the "Script Job as" and selected "Create To" and "New Query Editor Window". Once it was in the query editor window, I changed the name of the job and ran the code. It created an exact copy of the initial job on the same server. Success!

share|improve this answer
I copied a job and it didn't do exactly what I wanted. We use schedules, DTS packages, and many other elements. While this may work in theory, care should be used if the job is complicated as you may get unexpected results; in my case, the schedule for the original & copied job was co-mingled, which was not my intent. – JosephDoggie Feb 16 at 20:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.