How To Upgrade A Microsoft SQL Server EDOCS DM Database To SQL Server 2005

Product: Open Text eDOCS DM
Version: All
Task/Topic: Upgrade
Audience: Administrator
Platform: Microsoft SQL
Document ID: 134115
Updated: May 23, 2008
Application Note
How to Upgrade a Microsoft SQL Server
eDOCS DM Database to SQL Server
2005
Document Title
Application Note How to Upgrade a Microsoft SQL Server eDOCS DM Database to SQL Server 2005
Contents
Summary ...................................................................................................................... 1
Upgrade Tools ............................................................................................................. 2
In-place Upgrade - Automated Through the Microsoft SQL Server 2005
Upgrade Analysis Wizard. ................................................................................ 2
Side-by-Side Upgrade - Automated Through the Microsoft SQL Server
2005 Upgrade Analysis Wizard. ....................................................................... 2
Microsoft Copy Database Wizard .................................................................... 2
SQL Server Integration Services (SSIS) .......................................................... 2
Bulk Copy Procedure (BCP) ............................................................................ 3
Before the Upgrade ..................................................................................................... 4
Verify Database Owner........................................................................................... 4
Create DOCSADM Logon Account ........................................................................ 5
Create the DOCSUSER Logon .............................................................................. 8
Create the DOCSUSER Database Role ................................................................ 9
Grant the DOCSUSER Role Appropriate Rights .................................................. 11
After the Upgrade ...................................................................................................... 12
Create Indexes and Stored Procedures ............................................................... 12
Change Compatibility of Attached Databases ............................................... 13
Champion Toolkit Document www.opentext.com

Document Title
Summary
This document details the eDOCS DM requirements for upgrading a Microsoft SQL
Server database. This document is intended to cover eDOCS DM-specific issues; it
does not include step-by-step instructions for performing a SQL upgrade. You should
consult with Microsoft for detailed instructions on upgrading Microsoft SQL Server.
Microsoft offers several upgrade utilities, and is better able to assist you with an
upgrade of their product. NOTE: The information in this document is applicable for an
upgrade to Microsoft SQL Server 2005 from SQL Server 2000.
Champion Toolkit Document www.opentext.com 1

Document Title
Upgrade Tools
Listed below are the tools available for upgrading a Microsoft SQL Server database.
Under each tool is a list of benefits for each tool and limitations, if applicable. In
planning your upgrade, you will need to decide which tool best meets your needs. For
more detailed information, you should consult the Microsoft SQL Server 2005 Upgrade
Advisor.
In-place Upgrade - Automated Through the Microsoft SQL

Server 2005 Upgrade Analysis Wizard.
• Simplest method of upgrading a Microsoft SQL database.
• Mostly an automated process.
• Upgraded instance has the same name as the original, replacing the older
version.
• Existing SQL logons and users remain synchronized.
• Transfers stored procedures.
Limitations:
• Difficult to roll back.
• Clustered environments have special considerations.
Side-by-Side Upgrade - Automated Through the Microsoft

SQL Server 2005 Upgrade Analysis Wizard.
Microsoft Copy Database Wizard

• Easier to roll back since the original database server is untouched.
• Takes into account proper code page translation.
• Includes all database schema objects including users, roles, and indexes.
SQL Server Integration Services (SSIS)

• Allows you to export data from one database and import into another.
• Can be used for many database engines (for example, Microsoft SQL, Oracle,
Sybase, and other ODBC data sources).
• Allows you to massage the data as it is transferred.
Limitations:
• Cannot transfer all schema objects if source database is not Microsoft SQL 7.0
or 2000.

Document Title
• Does not do any data code page translation.
Bulk Copy Procedure (BCP)

• Used to extract data from a Microsoft SQL or Sybase database.
• Can extract data into a delimited ASCII text file or into native format.
• Also used to import data extracted via the two methods above or from a user-
created delimited ASCII text file.

Document Title
Before the Upgrade

Detailed in this section are tasks that you should complete before you begin your
upgrade of Microsoft SQL Server.
Verify Database Owner

Before you can upgrade Microsoft SQL Server, you must create a new database to
be used as your destination database. By default, when you create a new database
in Enterprise Manager, the database owner defaults to the account used to register
the SQL Server. If you registered your SQL Server using an account other than sa,
you must modify this information prior to creating your eDOCS DM database. eDOCS
DM requires that the database owner be the sa account. Listed below are instructions
to assist you with verifying and modifying the SQL Server registration:
1. Start SQL Server Enterprise Manager.
2. Under Microsoft SQL Servers, expand the SQL Server Group.
3. A list of registered SQL Servers appears; from the list of SQL Servers, select your
SQL Server.
4. Right-click, and then click Edit SQL Server Registration properties. The
following Registered SQL Server Properties dialog box appears.
NOTE: If your SQL Server is not listed, you need to register your
SQL Server and then complete step 4 above.

Document Title
Figure 1
5. From the Registered SQL Server Properties dialog box, under Connection,
click Use SQL Server authentication and type sa for the Login Name. NOTE: If
you did not assign a password to sa during installation, the default value is NULL
or blank.
6. Click OK to save your changes.
Create DOCSADM Logon Account

In an eDOCS DM environment, sa owns the database, and DOCSADM owns the
tables within the database. Therefore, after you create your destination eDOCS DM
database in Enterprise Manager, you should do the following to create the
DOCSADM logon account.
1. Start SQL Server Enterprise Manager. Under Microsoft SQL Servers, expand
the SQL Server Group.
2. A list of registered SQL Servers appears; from the list of SQL Servers, expand
your SQL Server.
3. A list of folders appears; expand the Security folder.
4. Select Logins, right-click, and then click New Login. The following SQL Server
Login Properties dialog box appears:

Document Title
NOTE: If the DOCSADM logon account already exists, right-click

the logon account, and then click Properties to display the
account properties for DOCSADM. Notice that you are unable to
change the Name or Authentication, but you can change the
password. Proceed to step 7 below to verify account settings.
Figure 2
5. Click the General tab and type DOCSADM for the Login Name.
6. Under Authentication, click SQL Server authenticationand enter a password
to be used with the DOCSADM account. By default, we recommend DOCSADM;
however, you may want to change this if you have security concerns. NOTE: For
details regarding the use of the DOCSADM or DOCSUSER logon accounts,
please see DM Suite Installation Guide, Hummingbird 2004, Chapter 5 - Generating
a Library.
7. Under Defaults, select your eDOCS DM database and leave the language set to
<Default>.

Document Title
8. Click the Database Access tab; the following dialog box appears:
Figure 3
9. Under Specify which databases can be accessed by this login, select your
eDOCS DM database from the Permit column. (See above example.)
10. Under Database roles for [your database name], the following database roles
should be selected:
• public
• db_accessadmin
• dB_securityadmin
• dB_ddladmin
• dB_backupoperator
• dB_datareader
• dB_datawriter

Document Title
NOTE: Do not assign the DOCSADM account any Server Roles

or the Database Role of db_owner; otherwise, the objects
transferred during the migration are owned by the wrong account,
and eDOCS DM does not function properly.
11. Click OK to save the configuration.
Create the DOCSUSER Logon

We do not recommend that you use the DOCSADM account as the common logon
account. The DOCSUSER account has sufficient privileges needed by most users of
eDOCS DM client applications. For a better understanding of both logon accounts
and logon schemes, please see DM Suite Installation Guide, Hummingbird 2004,
Chapter 5 - Generating a Library.
2. Under Microsoft SQL Servers, expand the SQL Server Group; a list of
registered SQL Servers appears. From the list of SQL Servers, expand your SQL
Server.
3. A list of folders appears; expand the Security folder.
4. Select Logins, right-click, then click New Login, and the following SQL Server
Logins Properties dialog box appears:
Figure 4
5. Select the General tab and under Name, type DOCSUSER.

Document Title
6. Under Authentication, click SQL Server authentication and enter the

password for the DOCSADM account.
7. Under Defaults, select your DOCS database and leave the language set to
<Default>.
8. Click the Database Access tab, and the following dialog box appears:
Figure 5
9. Under Specify which databases can be accessed by this login, select your
DOCS database under Permit.
10. Under Database roles for [your database name], select the checkbox for
“public” only. The DOCSUSER account only needs a public database-level role.
11. Click Apply and then OK to save the configuration. Focus is returned to the
Enterprise Manager console.
Create the DOCSUSER Database Role


Document Title
registered SQL Servers appears. From the list of SQL Servers, expand your
SQL Server.
3. A list of folders appears; expand the Databases folder.
4. Expand your DOCS database.
5. Right-click Roles, and then click New Database Role; the following Database
Role Properties dialog box appears:
Figure 6
6. Under Name, type DOCS_USERS.

7. Under Database role type, select Standard role and click Add.
8. Select the DOCSUSER role member and click OK.
9. Click Apply and then OK to close the Database Role Properties dialog box and
return to the Enterprise Manager console.

Document Title
Grant the DOCSUSER Role Appropriate Rights

The next step is to grant the DOCS_USERS Role the appropriate rights to all tables
and stored procedures owned by DOCSADM. You can accomplish this through
Enterprise Manager as follows:
registered SQL Servers appears. From the list of SQL Servers, expand your SQL
Server.
3. A list of folders appears; expand the Databases folder.
4. Expand your DOCS database and clck the Tables icon to display the data.
5. Right-click each table that is owned by DOCSADM and click Properties to
display the properties for that item.
6. Under the General tab, click Permissions.
7. Check all of the permissions for the DOCS_USERS Role.
8. Repeat Steps 1-7 for the Stored Procedures icon.
Alternatively, you can log on to the Query Analyzer (ISQLW.EXE) as sa and run the
following script on your DM database to accomplish the same tasks:
Declare curs1 cursor for select name from sysobjects where

uid=user_id('docsadm')
Open curs1
Declare @val varchar(30),@command varchar(254)
Fetch next from curs1 into @val
While @@fetch_status=0
Begin
select @command = "Grant all on Docsadm."+@val+" to DOCS_USERS"
exec(@command)
Fetch next from curs1 into @val
End
deallocate curs1

Document Title
After the Upgrade

During the upgrade, the indexes are not transferred; however stored procedures and
logon accounts are retained during the upgrade. Therefore, you must recreate the
indexes in your new database after the transfer is complete. Outlined below are
instructions for recreating the eDOCS DM indexes:
Create Indexes and Stored Procedures

To recreate the eDOCS DM indexes, you can run Library Generator (TBLCOMP.EXE)
against your new (or upgraded) database. Library Generator creates the default
eDOCS DM indexes and stored procedures. If you have added indexes to your
eDOCS DM database through eDOCS DM Designer® or otherwise, you must
recreate them manually.
NOTE: SQL Server 2005 does not include a SQL Server 2005
client; therefore if you do not have another SQL client installed, or
are not running SQL Server on the machine you are running
Library Generator from, you will receive an "Unrecognized SQL
client DLL" error message. Please see Open Text Knowledge
Base Article 12938315 for more information on this issue
Microsoft SQL Server 2005, by default, requires complex passwords when creating
new groups and users. When generating a new DM library, use complex passwords
for your DOCSADM and DOCSUSER accounts.
To enable support for Microsoft SQL Server 2005, you need to use a complex
password the first time you run Library Generator. A complex password is a password
that:
• Does not contain the user's account name, either in full or in part.
• Is at least six characters in length.
• Contains characters from three of the following categories :
English uppercase characters (A through Z).
English lowercase characters (a through z).
Numbers (0 through 9).
Nonalphanumeric characters (for example: !, $, #, %).
After running Library Generator, you can disable Password Policy Enforcement.
Please see Open Text Knowledge Base Article 12968515 for information regarding the
English version of Library Generator provided with DM 5.1.0.5 SR6 featuring support
for Microsoft SQL Server 2005. Refer to your SQL documentation for additional
information.

Document Title
Change Compatibility of Attached Databases

Remove the following entry from the PDOCS.INI file:
[Compatibility]
DbLib=8
Change the compatibilty of the attached databases to 80. You can log on to the
Query Analyzer (ISQLW.EXE) as sa and run the following script on your DM
database to accomplish this:
EXEC sp_dbcmptlevel @dbname = '<Database Name>', @new_cmptlevel = '80'

GO
Your upgrade of Microsoft SQL Server is complete. You should now ensure that each
end user has the Microsoft SQL client installed in order to connect to the new eDOCS
DM database. You should also ensure that all PCDOCS.INI files have been
redirected to the new eDOCS DM database. A good way to ensure that all users are
using the new database is to take the old database offline. It is very difficult to correct
problems that occur when a user has accidentally been using the old database.

Document Title
Sales Americas Europe Asia/Pacific

www.opentext.com United States Germany United Kingdom Australia
info@opentext.com 100 Tri-State Int’l Parkway Technopark 2 Grosvenor House Level 23
North America Sales Lincolnshire, IL Werner-von-Siemens-Ring 20 Horseshoe Crescent 100 Miller St.
USA 60069 D-85630 Grasbrunn Beaconsfield, Buckinghamshire North Sydney
1-800-499-6544
Phone: 847-267-9330 Germany United Kingdom HP9 1LJ NSW 2060
International Sales Fax: 847-267-9332 Phone: +49 89 4629 0 Phone: +44 1494 679700 Australia
+800-4996-5440 Fax: +49 89 4629 1199 Fax: +44 1494 679707 Phone: +61-2-9026-3400
Fax: +61-2-9026-3455
If you are an Open Text partner or customer, visit online.opentext.com for more information about this and other Open Text
solutions.
Open Text is a publicly traded company on the NASDAQ (OTEX) and the TSX (OTC).
© Copyright 2008 by Open Text Corporation. Open Text, Livelink, Livelink ECM, and Great Minds Working Together are trademarks or registered trademarks of Open Text Corporation. All other trademarks or
registered trademarks are the property of their respective owners. All rights reserved.
www.opentext.com 14

How To Upgrade A Microsoft SQL Server EDOCS DM Database To SQL Server 2005

Uploaded by

How To Upgrade A Microsoft SQL Server EDOCS DM Database To SQL Server 2005

Uploaded by

Product: Open Text eDOCS DM

Champion Toolkit Document www.opentext.com

Champion Toolkit Document www.opentext.com 1

In-place Upgrade - Automated Through the Microsoft SQL

Side-by-Side Upgrade - Automated Through the Microsoft

Microsoft Copy Database Wizard

SQL Server Integration Services (SSIS)

Champion Toolkit Document www.opentext.com 2

• Does not do any data code page translation.

Bulk Copy Procedure (BCP)

Champion Toolkit Document www.opentext.com 3

Before the Upgrade

Verify Database Owner

Champion Toolkit Document www.opentext.com 4

Create DOCSADM Logon Account

Champion Toolkit Document www.opentext.com 5

NOTE: If the DOCSADM logon account already exists, right-click

Champion Toolkit Document www.opentext.com 6

Champion Toolkit Document www.opentext.com 7

NOTE: Do not assign the DOCSADM account any Server Roles

11. Click OK to save the configuration.

Create the DOCSUSER Logon

5. Select the General tab and under Name, type DOCSUSER.

Champion Toolkit Document www.opentext.com 8

6. Under Authentication, click SQL Server authentication and enter the

Create the DOCSUSER Database Role

Champion Toolkit Document www.opentext.com 9

6. Under Name, type DOCS_USERS.

Champion Toolkit Document www.opentext.com 10

Grant the DOCSUSER Role Appropriate Rights

Declare curs1 cursor for select name from sysobjects where

Champion Toolkit Document www.opentext.com 11

After the Upgrade

Create Indexes and Stored Procedures

Champion Toolkit Document www.opentext.com 12

Change Compatibility of Attached Databases

EXEC sp_dbcmptlevel @dbname = '<Database Name>', @new_cmptlevel = '80'

Champion Toolkit Document www.opentext.com 13

Sales Americas Europe Asia/Pacific

You might also like