locked
Move Content and Configuration databases to a new SQL server? (WSS 2.0) RRS feed

  • Question


  • I am getting ready to test a WSS 2.0 to WSS 3.0 upgrade. Luckily our WSS 3.0 runs on vmware. So, I made a clone of the existing server and now I am going to test the upgrade in a lab type environment.

    The first thing I am trying to do on this clone is to point it to a copy of the Configuration and Content Databases. I used SQL server to restore our nightly backup to the test SQL server, now I am trying to attach WSS 2.0 to the new databases. For some reason, they won't attach. I am almost certain it isn't a security issue. I have checked permissions every which way possible. I was wondering "what is the correct procedure" for doing this? I searched the forum and found a nice one for WSS 3.0, but haven't found anything for WSS 2.0

    Any help is greatly appreciated!

    Thanks,
    Shayne
    Monday, July 28, 2008 5:53 PM

Answers

All replies

  • How are you trying to attach your WSS DB's? What error messages are you getting? Any errors in event logs? (Application & security)
    Are you using WSS configuration wizard?

    Regards
    Ivan Bondy - MCPD, MCDBA, MCSA, MCTS - Sharepoint consultant
    Monday, July 28, 2008 7:25 PM
  •  
    I have tried in Site Administrator and with command line. The configuration database seems to attach fine. It is the content database that errors. The Even Log error shows the datbase is still trying to connect to the "old" server "loch9" in the Siate Admin, I changed it to the new server "portal", but it didn't take... (even though it didnt give me any error, it didnt show the "normal" screen where it says "status ok".) Here is the Even Log error:

    #50070: Unable to connect to the database STS_Sharepoint_1 on loch9. Check the database connection information and make sure that the database server is running.

    Monday, July 28, 2008 7:41 PM
  •  Shayne,
    Check this article:
    http://technet.microsoft.com/en-us/library/cc288639(TechNet.10).aspx

    It should get you going quickly.

    Cheers
    Ivan Bondy - MCPD, MCDBA, MCSA, MCTS - Sharepoint consultant
    Monday, July 28, 2008 8:14 PM
  •  
    I figured out the problem.

    I was only changing the dontent datbase under the "default server" setting. I was not going into the actual virtual server and adding the content databaset there.. oops!
    Monday, July 28, 2008 8:29 PM
  • Shayne,
    Glad you got this going.

    Cheers
    Ivan Bondy - MCPD, MCDBA, MCSA, MCTS - Sharepoint consultant
    Monday, July 28, 2008 9:00 PM