﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Administering / SQL Server 2005  / Exporting SQL Job / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Wed, 19 Jun 2013 10:35:26 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>My recommendation is to use SSMS a newer flavor the better.  use the Object Explorer Details.  This allows you to highlight multiple objects.  Click on the Jobs tree on the server and the jobs will appear in Object Explorer Details.  Run the task to create script.  With minor editing you should be able to recreate jobs.Good luck.</description><pubDate>Thu, 06 Dec 2012 10:49:38 GMT</pubDate><dc:creator>erikskinner</dc:creator></item><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>create a simple ssis package in which you have a tool called "transfer job task" , if you want you can pick  the jobs or you can select all. and run the package ... boom  all your 150 jobs will be transffed with in a min or 2  .</description><pubDate>Tue, 08 Feb 2011 12:58:04 GMT</pubDate><dc:creator>altitude00</dc:creator></item><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>If you have anything that's server specific, such as operator names for email notification, then make sure they already exist on the target server. You can script them out &amp; copy them first.</description><pubDate>Mon, 22 Sep 2008 12:57:36 GMT</pubDate><dc:creator>homebrew01</dc:creator></item><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>Re: scripting jobs, you can script all the jobs in an instance into one file in SSMS if you click on "Jobs" in Object Explorer then highlight all the jobs in the Details panel, right-click and select "Script Job As...".Then you only have one script to run in the Server B.</description><pubDate>Mon, 22 Sep 2008 09:50:19 GMT</pubDate><dc:creator>Greg Charles</dc:creator></item><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>I believe you can use the copy database wizard to move jobs.Just set up a 'sacrificial' database, right click -- tasks -- copy databaseRun through the Wizard and I think you have the option to select agent jobs to copy.~CraigCraig OutcaltMCITP, MCDBA</description><pubDate>Sun, 21 Sep 2008 08:31:03 GMT</pubDate><dc:creator>SQLBOT</dc:creator></item><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>There are more than 150 Jobs are running, this is painfull task to copy the each jobs and pasting at the destination servers.I am using SQL Servef 2005 64 Bit and couldn't do multiple select also.Is there any script which will generate script for the jobs.Regards,Mohanraj Jayaraman</description><pubDate>Sun, 21 Sep 2008 05:17:59 GMT</pubDate><dc:creator>New2SQL-343122</dc:creator></item><item><title>RE: Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>Script all the jobs using Management studio in Server A and apply the script in Server BMake sure the output path is valid</description><pubDate>Sat, 20 Sep 2008 12:19:38 GMT</pubDate><dc:creator>Krishnaraj9</dc:creator></item><item><title>Exporting SQL Job</title><link>http://www.sqlservercentral.com/Forums/Topic573013-146-1.aspx</link><description>Hi,How to export SQL Jobs which under SQL Server Agent -&amp;gt; Jobs -&amp;gt; (All the jobs).Just want to export these jobs from Server A to Server B.I have already tried with msdb but unfortunatly it had failed to restored it.Thanks in advance for any inputs.Regards,Mohanraj Jayaraman</description><pubDate>Sat, 20 Sep 2008 09:17:20 GMT</pubDate><dc:creator>New2SQL-343122</dc:creator></item></channel></rss>