Nice tip, learned something new :)

Just came across this post and wanted to add - It's certainly a very interesting idea I want to try - cluster every SQL "physical" instance - that makes moving much easier when you move We are all SAN for physical anyway (but NFS for VM) - I was told by MSFT PFE recently some companied even P2V their 2-node cluster into a VM, and took ...

Thanks for the post Although I'd say upgrading from SQL 2008 Std to 2012 Std is not a big leap, especially the leap in licensing $$ (per socket to per core)

Too bad SQL Search doesn't work on SQL 2000, only on 2005/2008 but it's such a nice add-on to have for SSMS

SSMS Tools Pack http://www.ssmstoolspack.com/ Gotta have (especially if you don't want to pay for Red Gate SQL Prompt)

Good news, as we just bought Red Gate SQL Backup last month too :)

I totally agree with you, use CREATE to prevent modifying the procedure/code by accident

Ha, just installed the SP3 and 2 patches today Notes - they took quite a while (2 patches took about 30 minutes total) - You need to start the installer on the Active node of the cluster, and it'll stop the cluster service for you My SQL version is now Microsoft SQL Server 2005 - 9.00.4262.00 (X64)

Limitations of the Missing Indexes Feature 2005 Books Online http://msdn.microsoft.com/en-us/library/ms345485(SQL.90).aspx 2008 Books Online http://technet.microsoft.com/en-us/library/ms345485.aspx

Good thing is that most of the time, one can install SSIS afterwards, and WITHOUT restarting required I just installed one last week, needed to execute a SSIS package as SQL job