I'd also like to cast my vote for Last Page at the top ...

Don't forget to run the following:

• UPDATEUSAGE -- for the table
• sp_ercompile -- for the table
• sp_refreshview -- for each view on the table

Here's a handy little reference on the system tables  no DBA should be without:

http://www.microsoft.com/sql/prodinfo/previousversions/systables.mspx

Licensing should not be a major issue. The second instance just has to be the 'Devlopers Edition', so you just need the OS license. As for 2 SQL instances, Production and...

There is no 'secret' command. Stopping a long running rollback by erstarting SQL server (or rebooting the server iteslf) will only cause you to expend more time than you already...

I prefer land in Florida or swamp in Arizona ...

Key Question:

    --> Will the posters in this forum share in the proceeds if you win ???

All great questions. 100M rows on SQL Server today is not that huge. Depending on what the problem is maybe Analysis Server could be of assistance as well.

Try executing this command:

    DBCC SQLPERF(UMSSTATS)

How many CPUs does your SQL Server have ? Is is just dedicatde to SQL Server alone ? Have you tried to use perfmon to see what you can see...

Very interesting ... I have been able to duplicate it when using grid for output instead of text. It only occurs for SQL logins with the sysadmin role, not NT...

Good luck ... here's another site that may be of assistance as well: http://www.sqldts.com/ 

I just spot checked 4 of my 25 servers and did not find Sysadmin=0 in the query results ...

I'm on my second cup of coffee as well ...

... no problemo ...

(feeling very govern-ator-ish today)

I have not finished my coffee yet ... what am I missing here ?