Copy jobs

How best to copy jobs from test instance to production?Well, you can script them and then run scripts on the production...
MC
"Gerry M" <GerryM@.discussions.microsoft.com> wrote in message
news:D4148CA3-E474-4800-937F-2AD2D32CBDA6@.microsoft.com...
> How best to copy jobs from test instance to production?|||Is this SQL Server 2000? or SQL Server 2005? However, you may use object
transfer using DTS or "Transfer Job tasks" from toolbox of SSIS. (You may
also script out all the jobs and execute the script on the new box)
Few things to keep in mind:
Verify that you have appropriate owners for each job.
Verify that approriate databases have been selected for those jobs
Verify that notification properties are set to appropriate users (as it may
differ from test to production environment)
Hope this helps.
Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide Microsoft SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
Register (Free):
http://www.sqlcommunity.com/RegistrationLoginPage/tabid/68/Default.aspx?returnurl=%2fdefault.aspx
"Gerry M" wrote:
> How best to copy jobs from test instance to production?|||"Gerry M" <GerryM@.discussions.microsoft.com> wrote in message
news:D4148CA3-E474-4800-937F-2AD2D32CBDA6@.microsoft.com...
> How best to copy jobs from test instance to production?
SQL agent jobs? DTS Jobs? SSIS Jobs?
2000, or 2005?
Try a right-click on the job name and look for a script option. If the job
calls a procedure, then make sure that is installed first.
Other than that, you should have documented and scripted putting the job in
place on dev, or QA and then you wouldn't have had the problem to begin
with.