Post reply

SQL SERVER 2000 JOBS

  • December 3, 2008 at 11:34 am

    #94348

    Hi Everyone

    Can anyone please tell me the steps to migrate/move jobs between 2 SQL SERVER 2000 instances.

    Thanks

  • December 3, 2008 at 11:49 am

    #907071

    [font="Verdana"]Create a new DTS package and add 'Transfer Jobs task'- Used to copy jobs from an instance of SQL Server 7.0 or SQL Server 2000 to an instance of SQL Server 2000.

    --This came up in a Google search. Although, I used it for copying to 2k5 from 2k..never used it in 2k.

    Use copy database wizard to transfer the jobs

    Useful, if you are copying any other database also. But from what I read, the copy database wizard also creates a DTS package and runs the associated job.

    Reference:

    (a)http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/dtssql2k.mspx#ESE

    (b)http://support.microsoft.com/kb/274463

    [/font]

    -Hope is a heuristic search :smooooth: ~Hemanth

  • December 3, 2008 at 12:25 pm

    #907089

    If you're not comfortable creating a DTS package, you can script jobs in Enterprise Manager:

    Management -> SQL Server Agent -> Jobs

    Right-click on a job or jobs -> All Tasks -> Generate SQL Script

    Save the script then open it in a Query window in the destination instance and execute it.

    I've never heard of using the Copy Database Wizard to copy jobs.

    Greg

  • December 3, 2008 at 12:37 pm

    #907097

    Thanks for the reply !!

    I have one doubt , if i create the scripts for the job and execute it on the destination , will be job will get created there with the proper schedule( as on source server ) or do i manually need to create job . Or if you can tell me the steps it would be gr8 help

    Thanks

  • December 3, 2008 at 1:11 pm

    #907112

    The schedule is included in the job script. You don't need to create anything separately.

    Greg

  • December 4, 2008 at 8:36 am

    #907637

    I always use the Generate Script technique, it includes the schedules as well

    some notes

    - you may need to create Categories if you have some custom ones

    - you may need to create Operators if you have some (in 2005 or 2008, don't remember if 2000 has this Operator concept)

    - if some jobs involve some Databases and that don't exist on the new server, the job may not get created

    SQLServerNewbieMCITP: Database Administrator SQL Server 2005

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

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