Download Saving Replication Rules to Different Database Types in Designer

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Global serializability wikipedia , lookup

Microsoft Access wikipedia , lookup

Entity–attribute–value model wikipedia , lookup

Serializability wikipedia , lookup

Oracle Database wikipedia , lookup

PL/SQL wikipedia , lookup

Database wikipedia , lookup

Concurrency control wikipedia , lookup

Relational model wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Versant Object Database wikipedia , lookup

Database model wikipedia , lookup

Clusterpoint wikipedia , lookup

Transcript
Saving Replication Rules to Different Database Types in
Designer To save the replication rules to a different database type:
1. Verify replication compatibility between the different database types to be included in your Replication
Network. For more information, see "Validate Data Type Compatibility" on page46.
2. Select File > Save As. The Save As window appears:
3. In the Database Type field, use the drop-down menu to select the type of database you want to
replicate.
4. In the database location field, specify the attributes the Replication Engine uses to locate the
corresponding database. The attributes that comprise this value depend upon the type of database
schema you are defining a project for. For a list of valid location formats, see Table 2 on page22. Save
Replication Rules to Different Database Types Release 8.2 164
5. In the Database Connection Information section, enter the following information: • User Name — User
name or login ID the Replication Engine uses to access the corresponding database. Typically, pduser. •
Password — Password the Replication Engine user, pduser, uses to access the corresponding database. 6.
Click OK.
Saving Replication Rules to a Different Database Type using
prdc
To save the replication rules to a different database type, use the following command:
prdc SAVEAS|SA RelID NewRelTag [[-odbcn=odbcuser] [-odbcp=odbcpassword] [odbcc=odbcconnstr] -da=dbtype -db=connstr][-Force] [-PDL=pdlid] -RULEFILE=rule
where:
■ RelID
— Unique identifier for the release
■ NewRelTag
— Unique identifier or alias for this version of the project.
— User name or login ID the Replication Engine uses to access the corresponding database.
Typically, pduser.
■ odbcUser
— Password the Replication Engine user, pduser, uses to access the corresponding database.
■ odbcConnstr — Specifies whether the Replication Engine authenticates with Microsoft SQL Server
databases using Windows authentication or ODBC authentication.
■ Password
If you specify a value of Trusted for this attribute, the Replication Engine connects to your database using
Windows authentication.
If you do not specify the -odbcc parameter, the Replication Engine connects to your database using
ODBC.
— Type of database whose schema you are defining a release for. For a list of valid values, see
Table 2 on page22.
■ DBType
— Specifies the attributes the Replication Engine uses to locate the corresponding database.
The attributes that comprise this value depend upon the type of database schema you are defining a
project for. For a list of valid location formats, see Table 2 on page 22.
■ connstr
— Name of the developer license to associate with the corresponding project. You only need to
specify the -pdl parameter if you have multiple developer licenses on the same system.
■ pdlid
rule — Name of the rule file you are exporting the rules to. By default, the name of the rule file is
prdc.rul.
■