The Contact example

SQL Remote User's Guide
SQL Remote Design for Adaptive Server Anywhere
Partitioning tables that do not contain the subscription expression

The Contact example

The Contact database illustrates why and how to partition tables that do not contain the subscription expression.

Example

Here is a simple database that illustrates the problem.

Each sales representative sells to several customers. At some customers there is a single contact, while other customers have several contacts.

The tables in the database

The three tables are described in more detail as follows:

Table	Description
SalesRep	All sales representatives that work for the company. The SalesRep table has the following columns: rep_key An identifier for each sales representative. This is the primary key. name The name of each sales representative. The SQL statement creating this table is as follows: CREATE TABLE SalesRep ( Rep_key CHAR(12) NOT NULL, Name CHAR(40) NOT NULL, PRIMARY KEY (rep_key) )
Customer	All customers that do business with the company. The Customer table includes the following columns: cust_key An identifier for each customer. This is the primary key. name The name of each customer. rep_key An identifier for the sales representative in a sales relationship. This is a foreign key to the SalesRep table. The SQL statement creating this table is as follows: CREATE TABLE Customer ( Cust_key CHAR(12) NOT NULL, Name CHAR(40) NOT NULL, Rep_key CHAR(12) NOT NULL, FOREIGN KEY REFERENCES SalesRep, PRIMARY KEY (cust_key) )
Contact	All individual contacts that do business with the company. Each contact belongs to a single customer. The Contact table includes the following columns: contact_key An identifier for each contact. This is the primary key. name The name of each contact. cust_key An identifier for the customer to which the contact belongs. This is a foreign key to the Customer table. The SQL statement creating this table is: CREATE TABLE Contact ( Contact_key CHAR(12) NOT NULL, Name CHAR(40) NOT NULL, Cust_key CHAR(12) NOT NULL, FOREIGN KEY REFERENCES Customer, PRIMARY KEY (contact_key) )

Table

Description

SalesRep

All sales representatives that work for the company. The SalesRep table has the following columns:

rep_key An identifier for each sales representative. This is the primary key.
name The name of each sales representative.

The SQL statement creating this table is as follows:

CREATE TABLE SalesRep (
   Rep_key CHAR(12) NOT NULL,
   Name CHAR(40) NOT NULL,
   PRIMARY KEY (rep_key)
)

Customer

All customers that do business with the company. The Customer table includes the following columns:

cust_key An identifier for each customer. This is the primary key.
name The name of each customer.
rep_key An identifier for the sales representative in a sales relationship. This is a foreign key to the SalesRep table.

The SQL statement creating this table is as follows:

CREATE TABLE Customer (
   Cust_key CHAR(12) NOT NULL,
   Name CHAR(40) NOT NULL,
   Rep_key CHAR(12) NOT NULL,
   FOREIGN KEY REFERENCES SalesRep,
   PRIMARY KEY (cust_key)
)

Contact

All individual contacts that do business with the company. Each contact belongs to a single customer. The Contact table includes the following columns:

contact_key An identifier for each contact. This is the primary key.
name The name of each contact.
cust_key An identifier for the customer to which the contact belongs. This is a foreign key to the Customer table.

The SQL statement creating this table is:

CREATE TABLE Contact (
   Contact_key  CHAR(12) NOT NULL,
   Name  CHAR(40) NOT NULL,
   Cust_key  CHAR(12) NOT NULL,
   FOREIGN KEY  REFERENCES Customer,
   PRIMARY KEY  (contact_key)
)

Replication goals

The goals of the design are to provide each sales representative with the following information:

The complete SalesRep table.
Those customers assigned to them, from the Customer table.
Those contacts belonging to the relevant customers, from the Contact table.