November 19, 2007 at 1:19 pm
I've just migrated databases from SQL2000 to SQL2005 (new server, restored SQL2000 backups to clean install of SQL2005 and have set up the maintenance plans on the user databases.
But my job takes 2 hours longer than on SQL2000. When I review the plan history, the Check database Integrity step is says it takes 11 seconds but then the next step doesn't start for another 44 minutes. (If I run the TSQL it takes about 7 minutes)
The next step is the Reorganize Index which the log says takes 8 minutes but then following step doesn't start for another 1 hr 20 minutes.
The flow between the steps is set to completion but I have also tried success and it doesn't make any difference.
I'm so confused. What am I missing?
Thanks
K
November 20, 2007 at 10:02 am
K,
Thing that pops in my mind is what is the database compatibility level set at? Is it at 90 (SQL 2005) or something lower?
have you gone into the job properties (as they are vastly different from SQL 2000) and ensure your setup is correct?
Are you on SP2 for SQL 2005?
JTS
December 3, 2007 at 3:22 pm
Even if I schedule a job with just the TSQL to do the check, the history shows an 11 second duration. It's just not possible.
They are set to 9. The thing about the job is that there is only one step that represents the Maintenance Plan. I have to look under the Maintenance Plan history to get any details about each process in the plan.
December 10, 2007 at 2:17 pm
Are the jobs using the SQL 2000 Database Maintenance Plan wizard or the new SQL 2005 Integration Services (SSIS)
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply