1.1

Also note that this version of SQLFire supports joins only on co-located data. Instead of using partitioning in
all cases, you should consider having applications replicate smaller tables that are joined with other partitioned
tables.
Note: If multiple applications update the same row of a replicated table at the same time outside of a
transaction, the table data can become out of sync when SQLFire replicates those updates. Keep this
limitation in mind when using replicated tables.
Creating Replicated Tables
You can create replicated tables explicitly or by default, using CREATE TABLE statement.
SQLFire creates a replicated table by default when you execute a CREATE TABLE on page 476 statement and
you do not include a PARTITIONING clause. You can also explicitly create a replicated table using the
REPLICATE clause in the CREATE TABLE statement. For example:
CREATE TABLE COUNTRIES
(
COUNTRY VARCHAR(26) NOT NULL CONSTRAINT COUNTRIES_UNQ_NM Unique,
COUNTRY_ISO_CODE CHAR(2) NOT NULL CONSTRAINT COUNTRIES_PK PRIMARY
KEY,
REGION VARCHAR(26),
CONSTRAINT COUNTRIES_UC
CHECK (country_ISO_code = upper(country_ISO_code) )
) REPLICATE;
Because this command omits the SERVER GROUPS clause, the example creates the 'countries' table and
replicates it on members of the cluster that host data (all peers and servers in the default server group that set
the host-data property to true).
vFabric SQLFire User's Guide70
Managing Your Data in vFabric SQLFire