Reserved Table Names

Pervasive DataExchange Reserved Words and Table Names

DataExchange reserved words are keywords with special meanings when processed by the Replication Engine. These words cannot be used as database or table names in your applications. The following is a list of the Replication system table names used by DataExchange.

Table C-1

Replication System Table Names

ActivateInfo	dActHist	dActSite
dActTbl	dCmd	dCmdSite
dCnf	dFKey	dFragF
dFragI	dGrp	dIDB
dIDBDef	dKey	dLang
dMsg	dMsgLang	dPKey
dPrm	dPrmGrp	dPrmTyp
dQueue	dSched	dSchema
dSet	dSFSite	dSite
dSiteExt	dSiteLnk	dSiteSet
dSort	dTblChg	dTrn
dUsr	dUsrGrp	dUsrPrf
dVer	dWSTS

In addition to the system table names listed here, DataExchange creates a unique replication table for each user table in your database that you have marked for replication. Replication user tables created by DataExchange are named by preceding the original table name with PDC. For example, a table named Billing.MKD has a companion replication table named PDCBilling.MKD. DataExchange uses the PDCtablename convention to keep track of the replication database tables during replication.

In the event of tables with the same name in different folders, DataExchange creates a unique file name, similar to the naming convention used for log files. For example, two tables named Billing.MKD located in different directories would result in a table named PDCBilling.MKD and PDCBilling0.MKD.

Pervasive DataExchange requires that the replication tables created from selected user tables have unique names and be preceded by PDC. Pervasive PSQL limits table names to 20 characters. Replication table names created by DataExchange meet all of these requirements.

Note A database deployed for replication is allowed to include table names that start with PDC. However, if you add those tables to a replication template, DataExchange asks you to confirm that they are not files internal to the replication system.

Other Limitations

Pervasive DataExchange conforms to almost all of the same limitations and conditions implied in Pervasive PSQL. The following lists any known Pervasive DataExchange limitations that differ from those listed for the Pervasive PSQL ODBC Engine Interface.

Pervasive PSQL Feature	Pervasive DataExchange Limit or Condition
Database tables	4,800 (per replication network)

For the complete list of Pervasive PSQL ODBC Engine Interface limitations, see the ODBC Engine in the SQL Engine Reference.