The registration utility may be executed from any
workstation configured to connect to both the production
environment database and the ConfigLab environment
database.
In this example, we describe how to register a
ConfigLab
environment. We'll call the supported environment
database "CDXPROD" and the
ConfigLab
environment database "CDXCLAB".
A sample file MS SQL Server-compare-source.bat is
provided with an example for a
Compare Source
>registration.
Database security will need to be setup for the utility
to register.
Example:
CDXPROD - The database already has a user-id. CDXPRODUSER
defined and security has been generated for this user.
CDXCLAB - The database already has a user-id. CDXCLABUSER
defined and security has been generated for this user.
For the utility to register database CDXCLAB in database
CDXPROD, additional security needs to run.
In database CDXCLAB, add the user CDXPRODUSER:
exec sp_adduser ' CDXPRODUSER ',' CDXPRODUSER ','public'
Generate security for the user CDXPRODUSER in database
CDXCLAB.
Add an ODBC connection on the database server, called
CDXCLAB, with login id sa connecting to CDXCLAB.
Add an ODBC connection on the database server, called
CDXPROD with login id sa connecting to CDXPROD.
You may specify the following parameters on the command
line. If parameters are not supplied, the registration
utility prompts for them:
-
Information about the supporting environment
database:
-
-
Name of SQL Server data source (ODBC) for the
database
-
Password for the
sa account
-
Name of the Linked server in the supporting
environment
-
Name of the database
-
Application schema owner database user
-s CDXCLAB,{sa user
password},SF-PDNT-032,CDXCLAB,dbo
-
Information about the supported environment
database:
-
-
Name of SQL Server data source (ODBC) for the
database
-
Password for the sa account
-
Name of the Linked server in supported
environment
-
Name of the database
-
Application schema owner database user
-r CDXPROD,{sa user
password},SF-PDNT-022,CDXPROD,dbo
-
Action:
-
-
I-Install (register), U-Reconfigure (reregister),
D-Uninstall (deregister)
-
-a I
-
Environment type of the supporting environment:
-
-
CMPS-Compare Source, SYNT-Sync Target,
CLAB-ConfigLab, ARCH-Archive
-
-t CLAB
-
Environment reference code:
-
-
The environment reference used to track the
ConfigLab environment.
-
-e PROD-CONFIGLAB
-
Name prefix:
-
-
The prefix character used to reference database
tables in the ConfigLab environment. Note that this
character must not be C, S, or a name prefix used by an
existing supporting environment.
-
-n A
-
Environment description:
-
-
Description of the environment reference.
-
-d Production ConfigLab
-
Apply changes to the databases:
-
-
Specify this parameter to apply the changes
directly instead of writing them to a log file.
-
-u
-
Owner Flag:
-
-
Specify the Owner Flag for the application.
-
-o owner flag value
-
Log file name:
-
-
Specify the name of the log file if the parameter
above was not specified.
-
-l {log file name}
Note:
When you run a distributed transaction against a linked
server in Microsoft SQL Server 2000 on a computer that is
running Microsoft Windows Server 2003, the following settings
are required for Microsoft Distributed Transaction
Coordinator (MS DTC).
-
Click
Start
, choose
All Programs
, then choose
Administrative Tools
, then click
Component Services.
-
In the Component Services Wizard, expand
Component Services
, then double-click
Computers.
-
Right-click
My Computer
, then click
Properties.
-
Click the
MS DTC
tab, then click
Security Configuration.
-
In the
Security Configuration
dialog box, click to select the
Network DTC Access
checkbox.
-
Under
Network DTC Access
, click
Network Transactions.
-
Make sure that
DTC Logon Account
is set to
NT Authority\NetworkService.
-
Click
OK.
-
In the message box, click
Yes
to continue.
-
In the
DTC Console Message
dialog box, click
OK.
-
In the
System Properties
dialog box, click
OK.
-
Reboot the computer for these changes to take
effect.
Note:
Note In some cases, you must start the DTC service before
you start the SQL Server service so that the linked server
distributed queries work correctly.
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.