Hi,My company wants to move a database included with WSS 3.0 installation to a *separate* server.We want to have the database completely separated, on a different computer, on SQL Server 2005 installation.Unfortunately, I'm not sure If the sharepoint is configured as a "Web Front End" or "Stand-alone".All I know, everything currently is on the same computer, and we can connect to the live database using the following path:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\queryThe question is, how can we move the database toSQL Server 2005, on very different server, leaving the application untouched?Quick summary, we currently have:intranet:---Server A: (WSS 3.0) + [windows internal database /SSEE (not sure!)] + DOMAIN Xand we want to have:intranet:---Server A: (WSS 3.0) + DOMAIN X--- Server B: SQL Server 2005 + DOMAIN YPlease help us!

Hi,if i understand you correctly, you need to move the database running Internal database in one domain to a new SQL server in another domain.You could follow this steps:1. Install new SQL Server in a new domain(domain Y)2. Backup the SQL Internal Database3. Restore the SQL Backup to the new SQL Server4. Re-attach the moved DB to the Web Application using Central Admin or StsadmYou could follow the steps in this guide:http://www.sharepointforum.com/en-US/Wiki/Forms/DispForm.aspx?ID=7(copy/paste url in web browser)Hope this helps!Cheers, Daniel Bugday Web: SharePoint Forum Blog: Daniel Bugday's SharePoint Blog

Thank you for the replies!I did everything as you told me, but I have a problem with the final step (Re-attaching the moved DB to the Web Application).I removed the oldContent Databaseand succesfully added the new one.Since the DB is on remote location and I didn't know how to passSQL Authentication account toSTSADM, I usedCentral Administration Site to add it.Unfortunately, the application does not work (i getHTTP 404 error).Perhaps it only lost the connection to the database? If yes, is there any way to re-estabilish the connection, or force the application to use the newContent Database?

Check here for reference:http://technet.microsoft.com/en-us/library/cc288692.aspx Daniel Bugday Web: SharePoint Forum Blog: Daniel Bugday's SharePoint Blog

Hi,"Please note, that http://APP2:38080 doesn't work anymore in browser, because the database is detached -- maybe this is causing the problems?"-It could be, but if STSADM don't work, then there's probably a syntax error.Can you ping the URL?Cheers, Daniel Bugday Web: SharePoint Forum Blog: Daniel Bugday's SharePoint Blog

In order to move your database to a new server, follow this article: Start here: http://www.cjvandyk.com/blog/Articles/How-do-I---Move-my-SharePoint-databases-from-32-bit-SQL-Server-2005-x86-to-a-new-Instance-on-64-bit-SQL-Server-2008-R2-x64.aspx Not all thing apply to your case, but it should get you through.I trust that answers your question... Thanks C http://www.cjvandyk.com/blog

Hi, Pre-requisites for using a sepreate SQL server is that both servers SQL and SharePoint are domain members..... -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.

I followed your procedure when I needed to move a wss 3.0 database (on 32bit server using SQL studio 2005) to a sharepoint foundation installation on a 64 bit server running sql studio 2008 but I am getting a message: HTTP/1.1 200 OK Server: Microsoft-IIS/7.5 Date: Wed, 11 May 2011 14:52:58 GMT Connection: close What does that mean?