On my SQL 2005 version and my SQL 2008 versions, it accepts sp_rename for that index name:

USE tempdb

CREATE TABLE dbo.nasty_index_name_test ( c1 int )

GO

CREATE NONCLUSTERED INDEX [<Name of Missing Index,...

What do you mean "doesn't work"? It won't even initiate the rename process?

If the tables have identity columns, you can use $IDENTITY as the column name.

If not, you might have to dynamically generate the code based on unique indexes on the table...

You can rename an index through SSMS; just backspace over the old name, and type in the new one.

No, not CPU (except perhaps a tiny amount periodically to check it for activity).

Connections themselves have some RAM overhead.

But since creating/destroying connections is...

User dbs will definitely work ok to a later SP.

Master will definitely NOT work; master MUST be exactly the same version.

Not sure about msdb, but apparently same rules apply as...

Please try this 🙂 :

SET DATEFORMAT dmy

SELECT CAST('20120524' AS datetime)

SELECT CAST('2012-05-24' AS datetime)

The universally accepted date format for SQL Server is "YYYYMMDD" (as in 20120524), not YYYY-MM-DD, which different installations will treat differently (and some will error out).

SQL itself won't allow you to restore an older master db (not sure about the model db, but it likely doesn't contain critical data anyway). Something else must be...

Partitioning could indirectly help performance, as follows:

-- make it possible/faster to rebuild/reorg current yr's data only;

-- each partition can be separately specified as uncompressed/compressed (SQL 2008+ only).

Exactly Paul; well put.

I gotta say, those two statements seem contradictory 🙂 or you're on a terribly...

Either one.

Adding a rowversion column to every table would indeed be huge overhead for no real gain, since it likely would never be used. Eight bytes per row would...

True. I didn't explicitly mention it, but I meant using standard/approved methods, such as generating the legit commands:

CREATE LOGIN

EXEC sp_addlinkedserver

etc..

With the old master db there, you could get (almost)...

You should be able to restore the master db to a different db name, if you want to pull data from the old master db directly in the SQL 2008...