Aug 06
SQL Aliasing to the Rescue!
Tim Allison
After graduating in 1989 I worked as a consultant, then off to Herman Miller as a Network Admin, and finally landed at C/D/H. So ultimately 19 years! Wow!
I enjoy making life better: at home, at play and at work. Technology happens to be one of those areas. In the same manner helping those around me become better through sharing knowledge only results in a better place for us all.
Family is important to me. I am finding my granddaughter (yes, I have three grandchildren) is always on the top of my “love to spend time with” list.
More about Tim
Articles by Tim Allison
Recently I had to move databases from one SQL 2005 server to another. You can detach the database from the old server, and then attach it to the new server. This is the fastest method as the security moves within the database, however, you still need to add the security login to make the process complete. You can use this same method if you want to move the database and log files to a new location on the same SQL server–detach the database, move the MDF and LDF files to a new location, then attach them again. This should not affect the application using the database.
If you’re migrating databases to a new server there are cases when the application may have embedded references to the old server name. Such is the case with SharePoint (Microsoft Office SharePoint Server or Windows SharePoint Services). A recent article regarding the move of SharePoint databases to a new server illuminated the easy, and Microsoft supported, way to accomplish this. SQL aliasing to the rescue!
Instead of parroting the details, here is the link to follow: http://stsadm.blogspot.com/2008/06/moving-databases-easy-way.html.
Thanks Gary!