Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Move SP DB from One server to another

  Asked By: Bhavika    Date: Feb 16    Category: MOSS    Views: 1248

I need to move all the SP DB from one server to another server,
My scenario is
In the same box AD, SQL 2005 and MOSS is installed (not a standalone option its
installed as complete option)
Now i need to move the DB alone to another box
i mean now in one BOX AD and MOSS and in another BOX SQL
I need to cheive this please help me i found lots of article in net but i cant
acheve
could u please tell me reference site which is very helpfull for me

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Jason Anderson     Answered On: Feb 16

Moving the content databases is fairly easy. But moving the Config database
is very difficult, especially if it was installed on the first SharePoint
server in the Farm. Your best approach will be to backup all the databases
in SQL. Then build a new SharePoint Farm with the same configuration
pointing to the new SQL server. Then re-attach the backed up content
databases on the new SQL server.

 
Answer #2    Answered By: Uttam Vanjare     Answered On: Feb 16

technet.microsoft.com/en-us/library/cc512725.aspx explains the move  quite
nicely.

I did this last week again and it worked fine. The most relevant steps in that
article are:

1.Refer the farm to the new database server  by creating a sql  Server connection
alias.

a.Start the SQL Server Native Client Network Utility (%SYSTEM%\cliconfg.exe).

b.On the General tab, verify that TCP/IP is enabled.

c.On the Alias tab, click Add.

The Add Network Library Configuration dialog box  appears.

d.In the Server alias box, enter the name of the current instance of SQL Server.

e.In the Network libraries area, click TCP/IP.

f.In the Connection parameters area, in the Server name box, enter the new
server name and instance to associate with the alias, and then click OK.

g.Repeat steps a through f on all servers that connect to SQL Server.

We had some issues with custom code, but just changed those to the new SQL
Server instance name.

 
Answer #3    Answered By: Jack Carroll     Answered On: Feb 16

Just to throw my 2 cents in. I did this about a year ago and it was very
easy, but I have had a couple of times when I called Microsoft for support
on an unrelated issues, the MS Tech had never heard of doing this and was
very confused and kept focusing on this as a possible cause of the issue I
was having...

 
Answer #4    Answered By: Chandrabhan Agarkar     Answered On: Feb 16

What about SSP , user profiles and Enterprise search details

 
Answer #5    Answered By: Lonnie Cohen     Answered On: Feb 16

SSP can be moved fairly easily, just like other content dbs. I would just let
Profiles and Search re-initialize after the move  with a full import and a full
crawl.

 
Didn't find what you were looking for? Find more on Move SP DB from One server to another Or get search suggestion and latest updates.




Tagged: