Re: MOSS and move SQL database



These are some excellent directions and seem to be just what I need. Thanks a ton. I have hit a snag though...

The service SQL Server 2005 Embedded Edition is not listed in the services. There are several entries for SQL though. (I am sure it is using the express edition that comes with MOSS 07.)

On a test server I did the following.
sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E

I get the error

HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.


When I look at the SQL Server Configuration Manager I see the name OFFICESERVERS. Should I reference that in the command listed above?

Thanks again.


"Robert Zhao [MSFT]" <v-rozhao@xxxxxxxxxxxxxxxxxxxx> wrote in message news:PiFwzWjvHHA.2220@xxxxxxxxxxxxxxxxxxxxxxxxx
For this issue, please follow below steps to move all the content database.

Step One: Backup the web application and check the database
======
1.1 Start SharePoint 3.0 Central Administration and Click Operation Tab.
1.2 Click "Perform a Backup" under Backup and Restore.
1.3 Check the Farm to including all elements and make notes of all the
configuration database and content database name.
1.4 Select "Continue to Backup Options" and select "Full" backup, type the
file path for backup file location.
1.5 After finishes, check the file path for backup file location.

Step Two: Detach the Content Database
======
2.1 Download and install the SQL client and the Sqlcmd utility. These tools
are available in the latest feature pack for Microsoft SQL Server 2005. For
more information about the feature pack for Microsoft SQL Server 2005,
visit the following Microsoft Web site:
<http://www.microsoft.com/downloads/details.aspx?FamilyID=df0ba5aa-b4bd-4705
-aa0a-b477ba72a9cb&DisplayLang=en>
2.2 Control Panel -> Administrative Tools -> find the "SQL Server 2005
Embedded Edition (MICROSOFT##SSEE)" service and ensure it is already
started.
2.3 Click Start -> Run -> Type "cmd" (without quotation marks). Run the
following command:
sqlcmd -S \\.\pipe\mssql$microsoft##ssee\sql\query -E
If it succeeds, we should see 1>
2.4 Detach the database with following command:
1> exec sp_detach_db 'db_name' (db_name is content database name that you
would like to move database file to)
2> go
2.5 When it finishes, move the database files from
%systemroot%\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data (by default, you may further
verify it) to the new server. (both the .mdf and .ldf files are required to
be moved)

Step Three: Re-attach the content database to the new SQL Server
======
3.1 On the new server, Start SQL Server 2005 Management Studio with the SQL
Server 2005 instance.
3.2 Right-Click Databases and click Attach.
3.3 Click Add and add the .mdf and .ldf moved.
3.4 Re-attach the old content database to new SQL Server 2005.

Step Four: Connect the Content Databases again:
=======
4.1 Start SharePoint 3.0 Central Administration in the new server and Click
Application Management Tab.
4.2 Create a new web application without create site collection.
4.3 Select the new created web application and click "Content Databases".
4.4 Click "Add a content database"
4.3 Type the Database Server Name and the Content Database name (you have
just moved).
4.4 Click OK to re-connect the content database to web application.
4.5 If you encounter any error message to add content database, please use
stsadm tool to add the content database. At the command prompt, type the
following command to attach the content database, and then press ENTER:
cd %commonprogramfiles%\microsoft shared\web server extensions\12\bin>
stsadm -o addcontentdb -url http://URLofWindowsSharePointServicesSite
-databasename DatabaseName -databaseserver DatabaseServer.
Note: The placeholders in this command are defined as follows:

a. http://URLofWindowsSharePointServicesSite is the URL of the SharePoint
site that hosts the content database.
b. DatabaseName is the name of the database that you want to attach to the
new Web application.
c. DatabaseServer is the name of the computer that hosts the content
database.

If there is any questions, please feel free to post back.

Sincerely,
Robert Zhao
Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • Re: How to handle concurrency issue with better performance?
    ... Then for timestamp, it will be unique? ... Hitchhiker's Guide to Visual Studio and SQL Server ... We all work with relational database designs and more ... select command). ...
    (microsoft.public.dotnet.framework.adonet)
  • Error: 18456, Severity: 14, State: 16
    ... to connect to SQL Server 2005 Express Edition from the command line. ... CreateDatabase.sql when run in Management Studio successfully creates ... the database that I require so I know the error doesn't lie there. ...
    (microsoft.public.sqlserver.connect)
  • Error when Logging on - Error: 18456, Severity: 14, State: 16
    ... to connect to SQL Server 2005 Express Edition from the command line. ... CreateDatabase.sql when run in Management Studio successfully creates ... the database that I require so I know the error doesn't lie there. ...
    (microsoft.public.sqlserver.security)
  • Re: How to handle concurrency issue with better performance?
    ... Hitchhiker's Guide to Visual Studio and SQL Server ... that have been modified since they were pulled from the database. ... select command). ... I create stored procedure for the update command and assign ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: How to handle concurrency issue with better performance?
    ... Keep in mind that a timestamp column does not store a date/time value. ... Hitchhiker's Guide to Visual Studio and SQL Server ... We all work with relational database designs and more ... select command). ...
    (microsoft.public.dotnet.framework.adonet)

Loading