This solution is to be used when you are moving an SQL database that connects to DocuShare to another SQL Server.
Note: This solution assumes that you will be connecting to the same DocuShare server; you are only moving the location of the SQL server.
Note: This solution should only be performed by an administrator.
Note: The steps provided below should be followed in order.
Note: The examples provided in the steps are based on SQL 2005 screens, but other versions should be similar.
1. Backup the DocuShare Database Files
Note: The backup of the database files and the documents directory must be done at the same time so that the information contained is in sync.
Note: Please contact Microsoft for additional information on backing up the database.
From the Old SQL Server,
a. Stop DocuShare.
b. Stop the SQL.
c. Use your standard backup procedure to back up the Docushare.mdf and the Docushare_log.LDF files on your Old SQL Server.
Note: The installation directory for SQL may or may not be the same on all servers depending on your particular installation.
2. Verify TCP/IP Enabled on the New SQL Server
From New SQL Server,
a. Open the Microsoft SQL Server Configuration Manager
b. Expand the SQL Server Network Configuration and Select Protocols for MSSQLSERVER
c. Verify that TCP/IP status is Enabled
3. Enabling Windows and SQL Authentication Mode on the New SQL Server
From the New SQL Server,
a. Open the Microsoft SQL Server Manager
b. Highlight your SQL Server and right-click on Properties
c. Select Security, under the Server Authentication Heading
d. Select SQL Server and Windows Authentication Mode (Sometimes labelled Dual or Mixed Mode depending on the version of SQL)
e. Click the Ok button to apply the changes.
4. Attach the Database files to the New SQL Server
From the New SQL Server,
a. Attach the Docushare.mdf and the Docushare_log.LDF files that you backed up in Step 1.
5. Verify Full Text Indexing is Enabled on the New SQL Server
From the New SQL Server,
a. Open the Microsoft SQL Server Manager
b. Highlight your database, right-click and select Properties.
c. Select Files, under the Place a Check Mark in the Use full-text indexing checkbox.
d. Click on Ok Button to apply the changes.
6. Manual OSQL (Check Database) on the New SQL Server
Note: This test is mimicking what DocuShare is trying to do when it connects to SQL. It is very important that you are able to successfully log into SQL using the OSQL command before you proceed to Step 7, because if you proceed to Step 7 without the proper login information for DocuShare it will not be able to connect to the database and DocuShare will not start.
From the DocuShare Server,
a. Open a Command Prompt window.
Type OSQL -S servername -Usa -Psa and press Enter.
Note: servername = the host name of the computer, -U = database User name, -P = database Password
Note: If you installed an instance in SQL for DocuShare you will need to use the following command OSQL –S servername\instancename –Usa -Psa
b. If you have logged into SQL successfully then 1> prompt will be displayed.
7. Connecting DocuShare to the new SQL Server’s Database
Note: DocuShare will need to be stopped to perform this solution.
From the DocuShare Server,
a. Open a Command Prompt window.
b. Change into the <dshome>\bin directory.
Where <dshome> is replaced with the installation directory for DocuShare. The default installation path is C:\Xerox\DocuShare. Depending on your installation environment the path may vary.
c. Type dssetup and press Enter.
d. Confirm all the entries by pressing Enter until you get to the Database Types
e. You will need to change the following entries to match your new SQL server information
· Database Type
· Database Host (ServerName)
· Database user
· Database password
· Instance (if applicable)
· Instance name (if applicable)
f. Once the Database information has been changed to the new information press enter until you finish the configuration questions (pressing enter accepts the your previous settings)
g. A message stating that –success! Should be displayed.
h. Start DocuShare.
Solution Updated: December 10th, 2012
Solution ID: 283