January 10, 2008 at 10:43 am
I have just done an in-place upgrade of a sql2000 SP4 instance to SQL 2005. After the upgrade I applied SP2 and cumulative hotfix rollup 4, plus the SQL 2000 DTS designer components for backward compatibility.
all went well with the upgrade.
I then migrated the maintenance plan for the system databases to 2005 SSIS version, and find it includes tempdb! This causes the jobs to fail.
Have I come across anther maintenance plan faux pas on microsofts part or have I done something wrong? Should I have applied GDR2 before the cumulative roll up?
---------------------------------------------------------------------
January 10, 2008 at 3:38 pm
Can you just exclude Temdb?
Regards,Yelena Varsha
January 11, 2008 at 5:27 am
Yelena, I wish, but no. The maintenance plan migrate option has taken 'all system dbs' to include tempdb and no way in in the gui to remove it.
creating a NEW plan for 'all system dbs' from scratch in 2005 does not include tempdb, so this is a bug in the migrate wizard , whether its particular to cumulative rollup 4 I do not know.
workaround will be having to recreate the plan from scratch, which is a shame as extra work using migrate wizard should avoid. this
Still interested to know if anyone else has come across this, does it happen if at GDR2 (9.00.3054) and if a fix for it.
---------------------------------------------------------------------
January 11, 2008 at 9:15 am
Ok, then the answer to you problems is a "junior DBA"who will re-create your plans. You don't really want Microsoft's "junior DBA" sittin' there and fixin' migration wizards 🙂 😛
Regards,Yelena Varsha
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply