SQL contd..
So never delete the c:\windows\installer directory or its contents, you’ll learn how unsuccessful you’ll be at installing a SQL service pack.
See for yourself if your SQL installation is bad, try the SP reinstall and sections will fail due to missing packages.
HAve maintenance plan failures when creating a new plan? Invalid column name ‘from_msx’.
Invalid column name ‘has_targets’. (Microsoft SQL Server, Error: 207)
SELECT SERVERPROPERTY(‘ResourceVersion’) as ResourceDB, SERVERPROPERTY(‘ResourceLastUpdateDateTime’) as ResourceDBLastUpdate,
SERVERPROPERTY(‘ProductVersion’) as Ver, SERVERPROPERTY (‘ProductLevel’) as SP;
GO
If your results show a Resource DB version that is different than your SQL Version, then you have a messed up install, probably due to the SP not installing correctly. Ensure you have your windows\installer directory, luckily I saved mine to another drive in case I needed it again. Also check to make sure your permissions are right on where your SQL DBs are at. Make sure your SQL local groups contain the correct user for which the SQL AGent and server are running as.
Keep your other sys db’s with Master!
ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= “R:\sqldata\mssqlsystemresource.mdf”)
ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= “S:\sqldata\mssqlsystemresource.ldf”)