We currently have a "stand-alone" deployment of MOSS, which was oringinally going to be used for development/testing, however it appears that has taken a life of its own. The development site now has production data and we need to migrate the data (or DB) to a server farm deployment, which will housed on different hardware. Is there a way to get the data out of the stand-alone edition and place it into a farm "production" version Any help, direction or insight is greatly appreciated. Thanks for your time.
Thanks,
JZavala
MOSS 2007 Stand-Alone upgrade/migration to Web Farm
Hot Topic
- Could not find the CSF-Administration-OU Organizational Unit in Active Directory
- Windows service not running from installer
- Anonymoys access question
- Accessing a SQL Server table using sql authentication as opposed to windows authentication
- Change background color
- InfoPath Forms with managed code with Workflows
- HelloWorld sample not working
- Database Connection - Stored Procedure
- What is the scope of static webservice object
- can we debug sharepoint execution
SharePoint Products
- How do you close tasks that are created inside a replicator?
- InfoPath Forms with managed code with Workflows
- Ways to implement and use metadata
- Multilanguage Forms
- Windows Operative System Architecture
- Documenting a web site
- O/R Mapping and visual controls
- re u familiar with RenderPattern for custom field type definition
- how to create folder or file on user's lacal c: drive
- Problems with Owner Draw Menus in an out of process ActiveX Document Server
MOSS 2007 Stand-Alone upgrade/migration to Web Farm
Bobby Patrick
I believe you have to be AT the server. The MSDE install won't allow remote connections.
Just stop the SQL service and move the .mdf and .ldf files to the new database server. Then continue with the process as descibed above.
Chrisull
You could do this by moving the content database from your testing environment to production which will take the entire site structure and content.
To do this, go into the SharePoint administration section and within the content databases section, set the content database related to your test site to offline. You may need to recycle the IIS process to release the database connections complete. If you are running the Microsoft#SSEE instance, follow this blog entry to detach the database through SQLCMD otherwise, just use the SQL Server Management Studio to detach the database.
Copy the database from the test server to the live environment and then attach it using the Management Studio. Now go into your live SharePoint administration and remove any existing database and then select to Add a new Content and attach the new database. If the database is too large, it will tell you to use the STSADM addcontentdb operation instead.
This worked fine for me when I wanted to move from the SSEE instance to a full copy of SQL Server 2005.
If you just want to move one site, trying using the SharePoint Designer which has an Export and Import Site server tool.
Helder Santos
Pome Alan,
Thank you for your quick reponse. However, I have tried to detach the DB through both the cmd and the MGT Studio and I keep receiving the error that "SQL Server does not allow remote connection." when I try to connect the SSEE db/instance. Any other suggestions
Thanks,
JZavala
navarrodj
We also had problems with DB migration - everything works fine, but when trying to access a site (no matter which one) you receive an error http 500...
It's very frustrating to find out that the most basic action - migration - doesn't work properly