Sql-server – Move all sharepoint 2007 databases to a new Sql Server

sharepoint-2007sql server

In our organization we have a Microsoft Sharepoint 2007 installed and configured on a Windows Server 2003 Standard Edition (32 bit).
The database had been installed and configured on a Sql Server 2000 (Windows 2000 Server 32 bit).
Now we are in the process to move all the databases from the Sql Server 2000 to a new Windows 2008 Server R2 Enterprise (64bit).
The new server has been already installed and doesn't have the same name of the Sql Server 2000.
We would like to upgrade all the Sharepoint 2007 database to the RDBMS so that we can dismiss the old, slow Sql server 2000.
Has anyone tried to do something similar?

Best Answer

You should do the following steps:

Backup all content and configuration databases. Backup your SSP databases.
Prepare content databases for moving.
Delete all the content databases.
Stop the SharePoint Farm by stopping a Timer, Tracing, Administration service
Copy mdf files of an old config database to a new SQL server
Attach SharePoint_Config database on a new server from copied mdf files.
Run stsadm -o renameserver -oldservername OLDSERVER -newservername NEWSERVER
Start all the SharePoint services stopped in 4.
Copy mdf files of content databases to a new server and attach these databases.
Attach content databases.
Add a content databases from a new SQL to SharePoint with stsadm or Central Administration
Restore an SSP databases
Create a new SSP using Restore command from an SSP database on a new SQL server.
Delete an old SSP.

Syntax:

ALTER TABLE {TABLENAME} 
ADD {COLUMNNAME} {TYPE} {NULL|NOT NULL} 
CONSTRAINT {CONSTRAINT_NAME} DEFAULT {DEFAULT_VALUE}
WITH VALUES

Example:

ALTER TABLE SomeTable
        ADD SomeCol Bit NULL --Or NOT NULL.
 CONSTRAINT D_SomeTable_SomeCol --When Omitted a Default-Constraint Name is autogenerated.
    DEFAULT (0)--Optional Default-Constraint.
WITH VALUES --Add if Column is Nullable and you want the Default Value for Existing Records.

Notes:

Optional Constraint Name:
If you leave out CONSTRAINT D_SomeTable_SomeCol then SQL Server will autogenerate
a Default-Contraint with a funny Name like: DF__SomeTa__SomeC__4FB7FEF6

Optional With-Values Statement:
The WITH VALUES is only needed when your Column is Nullable
and you want the Default Value used for Existing Records.
If your Column is NOT NULL, then it will automatically use the Default Value
for all Existing Records, whether you specify WITH VALUES or not.

How Inserts work with a Default-Constraint:
If you insert a Record into SomeTable and do not Specify SomeCol's value, then it will Default to 0.
If you insert a Record and Specify SomeCol's value as NULL (and your column allows nulls),
then the Default-Constraint will not be used and NULL will be inserted as the Value.

Notes were based on everyone's great feedback below.
Special Thanks to:
@Yatrix, @WalterStabosz, @YahooSerious, and @StackMan for their Comments.

Sql – How to return only the Date from a SQL Server DateTime datatype

SELECT DATEADD(dd, 0, DATEDIFF(dd, 0, @your_date))

for example

SELECT DATEADD(dd, 0, DATEDIFF(dd, 0, GETDATE()))

gives me

2008-09-22 00:00:00.000

Pros:

No varchar<->datetime conversions required
No need to think about locale

Best Answer

Related Solutions

Sql – Add a column with a default value to an existing table in SQL Server

Syntax:

Example:

Notes:

Sql – How to return only the Date from a SQL Server DateTime datatype

Related Topic