Both Service Pack 3 and Service Pack 3a for SQL Server 2000 failed during installation on one of our servers, both times while running script "sp3_serv_uni.sql". The server was previously running on Service Pack 2. The error message, as reported in sp3_serv_uni.out..... Creating 'system_function_schema.fn_get_sql'. Msg 2714, Level 16, State 6, Server SPMSVR, Procedure fn_get_sql, Line 15 There is already an object named 'fn_get_sql' in the database. However, a query search on the master database reveals no such object exists: select * from sysobjects where xtype = N'TF' and uid = USER_ID('system_function_schema') and name = 'fn_get_sql' I have read that some others have experienced similar problems with SP3, caused by .NET's MDAC 2.8 This kind of problem was sorted in SP3a but did not solve my problem. Furthermore, it appears that, since the failed SP3 upgrade, I can no longer rename any database objects in user databases. I can create and delete objects and perform any other administrative functions attempted so far, but cannot rename objects. Enterprise Manager simply reports "Cannot rename object" while Query Analyzer (in Northwind DB for example) reports: Object 'customers' does not exist or is not a valid object for this operation. A DBCC checkdb on all my databases (system and user) reports no errors. Is it possible that some part of the failed SP3 upgrade script has set a system flag that was not rolled back ? Any help on either the SP3 problem or the object renaming problem would be appreciated.