1.1.1

Table Of Contents
Syntax
[ SERVER GROUPS ( server_group_name [, server_group_name ]* ) ]
Description
The default group is specied in the DEFAULT SERVER GROUP directive of the CREATE SCHEMA on page
490 statement. If no server group is specied for the schema, the implicit default server group is used, which
includes all servers in the distributed system.
The server group names that you specify are converted to all-uppercase characters.
Note: In order for two partitioned tables to be colocated, the SERVER GROUPS clauses in both CREATE
TABLE statements must be identical.
Replicated tables must specify the same server groups, or one table's server groups must be a subset of
the other table's server groups.
You can congure both partitioned tables and replicated tables to use a gateway sender. However, you
must create replicated tables in the same server groups as the gateway sender(s) that you specify in the
CREATE TABLE statement. See Syntax on page 484.
Example with SERVER GROUPS Clause
CREATE TABLE COUNTRIES
(
COUNTRY VARCHAR(26) NOT NULL,
COUNTRY_ISO_CODE CHAR(2) NOT PRIMARY KEY,
REGION VARCHAR(26),
) SERVER GROUPS (SG1, SG2)
GATEWAYSENDER Clause
The GATEWAYSENDER keyword associates the new table with one or more named gateway senders, so that
DML operations against the table are replicated to the remote SQLFire cluster associated with the sender(s).
Note: You can optionally use the SQLFire ALTER TABLE command to add or remove gateway senders
after you have created a table.
Syntax
[ GATEWAYSENDER ( sender-name [,sender-name ] * ) ]
Example with GATEWAYSENDER Clause
The following example associates a table with the gateway sender, TEST_SENDER.
CREATE TABLE TESTTABLE
(
ID INT NOT NULL,
DESCRIPTION VARCHAR(1024),
ADDRESS VARCHAR(1024)
)
GATEWAYSENDER(TEST_SENDER)
The following example associates a table with two gateway senders in the system.
CREATE TABLE TESTTABLE
(
ID INT NOT NULL,
DESCRIPTION VARCHAR(1024),
503
SQL Language Reference