MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Database server migration - renaming database server in SharePoint 2007

  Asked By: Pallavi    Date: Sep 17    Category: MOSS    Views: 3328

We are migrating our SharePoint databases to a new database server. This new
database server will have a new name for SharePoint to reference. How do I go
about pointing SharePoint 2007 from the old database server name to the new

It seems like there should be a simple solution, but I have yet to find a solid



7 Answers Found

Answer #1    Answered By: .net Guru     Answered On: Sep 17

The simplest solution would be if you had built your original system using
an SQL alias. Then all you would need to do is move the physical databases
and change which server the alias was pointing to. That's why its normally
a best practice to always use SQL aliases when doing a SharePoint install.
Since it appears that you didn't use aliases, it's a little more difficult.
Moving your content databases is fairly easy. You can just detach them,
back them up, restore them to the new server and then re-attach them using
the new location. But you can't do that with the configuration database.
Take a look at the following blog post for more info.


Answer #2    Answered By: Renata Burt     Answered On: Sep 17

Unfortunately when this farm was originally configured the db alias option was
overlooked or not literally recommended at the time 3 years ago. I'm the one
who set up this farm originally, I reviewed MS documentation available at the
time and do not see a reference to using a db alias during installation. Oh
well, that is water under the bridge.

I will review the link you sent. I also was referred to this link:


It's a newer procedure, but still does not give an example that is like my
requirement. I may have to create a hybrid solution.

Hopefully I can come up with a solution that includes a db alias.

Answer #3    Answered By: Lazaro Rutledge     Answered On: Sep 17

It is a newer link, but you'll notice that step 11 requires creation of a
SQL alias that uses the same name as the existing SQL server. This will
only work if you are deactivating the existing server when moving the
database. So you will be physically moving the databases, but all the
naming will remain exactly the same as it is now.

Answer #4    Answered By: Karin Kerr     Answered On: Sep 17

I noticed that as well. Since in this solution I will not be changing the db
server name configuration in SharePoint, I have other concerns.

The current database server configuration is "ds1prodmoss\moss,1437". Will this
format convert to an alias name. My concern is whether I can use a '\'
character in the alias name and also indicate the port number as part of the
alias name? Does the alias point directly to the instance or does the instance
get appended to the alias name? And the same with the port number. Will an
alias name such as this be invalid?

Answer #5    Answered By: Vinod Kumar     Answered On: Sep 17

You'll have to try it. I normally use an alias so that I don't have to
include the instance name, since that can cause some issues in SharePoint
2010. Whichever way you go I don't think you would use the port number as
part of the alias.

Answer #6    Answered By: Jeffery Hayes     Answered On: Sep 17

I've successfully aliased a named instance before. I've also been on a
non-standard port. Should work. Give it a try

Answer #7    Answered By: Mohini Tiwari     Answered On: Sep 17

I've successfully created an alias for a named SQL instance before too. In
fact I consider that a Best Practice when working with SharePoint. But what
I wasn't sure you could do was name an alias as though it were a named