Use the WITH CRCOLS keywords to create two shadow columns that Enterprise Replication uses for conflict resolution. The first column, cdrserver, contains the identity of the database server where the last modification occurred. The second column, cdrtime, contains the time stamp of the last modification. You must add these columns before you can use time-stamp or UDR conflict resolution.
For most database operations, the cdrserver and cdrtime columns are hidden. For example, if you include the WITH CRCOLS keywords when you create a table, the cdrserver and cdrtime columns have the following behavior:
SELECT * from tablename
To view the contents of cdrserver and cdrtime, explicitly specify the columns in the projection list of a SELECT statement, as the following example shows:
SELECT cdrserver, cdrtime FROM tablename
For more information about how to use this option, refer to the IBM Informix Dynamic Server Enterprise Replication Guide.
Use these options to specify the storage location, distribution scheme, and extent size for the table. This is an extension to the 3ANSI/ISO standard for SQL syntax.
Storage Options: |--+-----------------------------+------------------------------> +-IN--+-dbspace---------+-----+ | | (1) | | | +--------dbslice--+ | | | (2) | | | '--------extspace-' | | (3) | '-| FRAGMENT BY Clause |------' >--+----------------------------+-------------------------------> | (2) (4) | '--------| PUT Clause |------' >--+------------------------------+-----------------------------| | (5) | '-| EXTENT SIZE Options |------'
Element | Description | Restrictions | Syntax |
---|---|---|---|
dbslice | Dbslice to store the table | Must already exist | Identifier, p. Identifier |
dbspace | Dbspace to store the table | Must already exist | Identifier, p. Identifier |
extspace | Name declared in the onspaces command to a storage area outside the database server | Must already exist | See documentation for your access method. |
If you use the USING Access-Method Clause (IDS) to specify an access method, that method must support the storage space.
You can specify a dbspace for the table that is different from the storage location for the database, or fragment the table among dbspaces, or among partitions of one or more dbspaces. If you specify no IN clause nor fragmentation scheme, the new table resides in the same dbspace where the current database resides.
In Dynamic Server, you can use the PUT clause to specify storage options for smart large objects. For more information, see PUT Clause (IDS).