Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Does anyone know the best way to do that? I couldn't find any articles on this subject.

share|improve this question

migrated from Jan 19 '10 at 12:12

This question came from our site for professional and enthusiast programmers.

Not really a programming question - try – Chris Latta Jan 19 '10 at 1:45

There are a couple of options to do this. The first (Microsoft-approved) way of doing it is to just move the content databases, but leave the config database on the internal database. The technet documentation for doing that is here:

If you want to move the config database as well, you have 2 options. The first (probably less headache-inducing) method is to basically backup your content databases, remove the WIDB from the computer, create a new farm pointing to your SQL Server database, then attach your content databases to the new farm. 2 blog posts that talk about using this method are here:

The second option is to actually try and move all the databases (including the configdb) to the new server. Microsoft has documentation on how to do this (not specific to WIDB->SQL Server migrations, but I don't see why it wouldn't work.) My understanding of this though is that moving the configdb is not always seamless, and could cause you some big problems. Regardless, here is the documentation for this approach:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.