Quickie post this morning. I was in a review of customer support cases yesterday lunchtime and noticed a trend of cases where people get into trouble moving databases around. There is a good KB article (http://support.microsoft.com/kb/224071/) which explains how to do this for user databases, master, model, tempdb and msdb. It also contains a link to a SQL Server 2005 hotfix for the problem where after detaching a databases that resides on network-attached storage, it can't be reattached.
Well worth reading to avoid downtime and a support call.
Anonymous comments are disabled
About Paul Randal - MSFT
Paul started in the industry in 1994 working for DEC on the VMS file system and check/repair tools.
In 1999 he moved to Microsoft to work on SQL Server, specifically on DBCC. For SQL Server 2000, he concentrated on index fragmentation (writing DBCC INDEXDEFRAG and DBCC SHOWCONTIG) plus various algorithms in DBCC CHECKDB. During SQL Server 2005 development Paul was the lead developer/manager of one the core dev teams in the Storage Engine, responsible for data access and storage (DBCC, allocation, indexes & heaps, pages/records, text/LOB storage, snapshot isolation, etc). He also spent several years rewriting DBCC CHECKDB and repair. For SQL Server 2008, Paul managed the Program Management team for the core Storage Engine to become more focused on customer/partner engagement and feature set definition.
In 2007, after 8.5 years on the SQL Server team, Paul left Microsoft to join his wife, Kimberly Tripp, running SQLskills.com and pursuing his passion for presenting and consulting.
Paul regularly presents at conferences and user groups around the world on high-availability, disaster recovery and Storage Engine internals. His popular blog is at http://www.sqlskills.com/blogs/paul/.
