Initially when I named my PC I picked the generic "StudioXPS" which is the model of dell, or so I thought I did. Actually I named it "SudioXPS" as if I am a huge Phil Collins fan... I know it's a pain to change names, and the places that machine name gets carved in stone, but the OCD kicked in and I NEEDED to fix it. And, as expected, SQL Server wasn't so happy.

SQL Learnings: Can't Modify/Delete Maintenance Plans in SQL 2005 after Rename:

After renaming SQL Server 2005 server the maintenance plans couldn't be deleted. When trying to delete or modify a plan user gets an error. Using the SSMS there is no way to delete the plan. I thought it might a similar issue to I had encountered with SQL Server 2000 Jobs (link); so I searched to see if Maintenance plans table was storing server name and couldn't find anything.

Not so fast, my machine didn't even seem to like that, so let's manually delete all jobs first:

Sql Server 2005 Delete Maintenance Plan Error « Gediminas (Gedas) Gudenas:

Below is the manual SQL fix to address this error: Drop failed for Job ‘XXXXXXXXXXXXX’. (Microsoft.SqlServer.Smo) The DELETE statement conflicted with the REFERENCE constraint “FK_subplan_job_id”. The conflict occurred in database “msdb”, table “dbo.sysmaintplan_subplans”, column ‘job_id’. The statement has been terminated. (Microsoft SQL Server, Error: 547)

Then back to the first page, and voila! We're ready to do the Maintenance Plan Wizard from scratch. Thanks Hive Mind that we call the Interwebs! *bawk* *bawk*