August 3, 2009 at 1:27 pm
I am moving my sql 2000 jobs to sql 2008 on a new server. I scripted them from 2000 and ran the script on the 2008 server. It seemed to execute the script ok with no errors and created all the jobs successfully. The issue I have is that every step of every job did not appear to add the database context for where to execute the step's command. The correct databases exist with all the sp's and tables that go with each step. They also show in the pull down box. Has anyone else experienced a problem with this and is there a known fix?
Thanks
Mickle
August 3, 2009 at 1:43 pm
Did you try using Microsoft upgrade advisor for SQL Server 2008. It will check the maintenance plans and SQL Agent jobs for conversion to SQL 2008 and compatibility.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
August 3, 2009 at 2:50 pm
In the script that you ran, are the database names listed correctly?
August 4, 2009 at 6:16 am
I had been trying to install the upgrade advisor but am running into some OS problems in getting it installed. I am still working on that but have not had success yet. As for the script, I created it from our working server which lists the dbases correctly and I checked the scrpt on some of my steps and it does contain the correct @database_name=N'xxx'.
Thanks
Mickle
August 4, 2009 at 6:24 am
Heres one more strange thing that I noticed this morning. One or two of the jobs do contain the database name but they were ones we created on the master?????
August 4, 2009 at 1:13 pm
By any chance is the new server case sensitive, and the old server can insensitive?
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply