Restoring Jobs in SQL 2000

Does anyone know where the jobs are stored in SQL 2000? The reason I'm asking is because we recently replaced a server and installed SQL 2005 on it. Apparently, the old server had some SQL jobs on it that I need to recover (not backup jobs or shrink jobs, but other types).

I have a full backup of the entire server done with Backup Exec 11d.  Do I need to restore the entire server or is there another way to find and restore just the jobs from 2000 to our new 2005?
LVL 1
megninAsked:
Who is Participating?
 
Nathan RileyFounderCommented:
I would just restore it then go into enterprise manager and right click jobs and create a script then drop that into a query window on 2005 and execute it.
0
 
Nathan RileyFounderCommented:
Restore the jobs or DTS packages?  If DTS packages I believe you have to save them as a structured storage file from within enterprise manager.  Which would mean you need to restore the server.
0
 
Nathan RileyFounderCommented:
As long as the backup program restores everything including packages.  I know a normal backup will not save the DTS packages.
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
megninAuthor Commented:
Are the Jobs stored in the file system like in C:\SERVER\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\JOBS   ?

Where we could restore that file and then look at it to recreate the job on the new server?
0
 
megninAuthor Commented:
Yeah, we want to try to avoid having to restore the server (300GB backup) over our slow network.  We would like to be able to use Backup Exec to pull an appropriate file from the file system.  We just don't know what that file would be of if that's possible.
0
 
Nathan RileyFounderCommented:
I believe that is your only option at this point.
0
 
megninAuthor Commented:
Bummer.  ;-)
0
 
Nathan RileyFounderCommented:
Hey better then doing it all from scratch if you have many jobs.
0
 
megninAuthor Commented:
No, there's only one job that we forgot about when we upgraded from 2000 to 2005.  It belongs to some application that interfaces with our Financial software.  
It just seems weird that you can't just pull a file out of C:\SERVER\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\JOBS and either read it if it's just text and re-create it on the new server or something.  Restoring an entire server for that just seems like 2 Billion times overkill.
0
 
megninAuthor Commented:
Thank you.  We'll have to remember to do that in advance next time.  ;-}
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.