The following guidelines are for designing and implementing multiple catalogs used for synchronization:
▪ When creating a database, solidDB creates a default catalog for the database.
▪ Besides the default catalog, a single solidDB database can contain other catalogs.
▪ If you do not explicitly CREATE and SET any catalogs, then you will use the default catalog for the database.
▪ Each catalog of a database can be either a master catalog, replica catalog, or both.
▪ Each catalog can contain multiple schemas. Transactions can access database objects in any catalog.
▪ A catalog can contain local tables as well as tables that are synchronized with a master database. A single transaction can use a combination of local database tables and master database tables.
▪ The physical database has a set of defined local users that have access to the local data management functions. For accessing the data synchronization functions, each catalog has one or more master users that have been downloaded as part of a replica registration.
To create and set catalogs for masters and replicas, use the CREATE CATALOG and SET CATALOG statements, see CREATE CATALOG and SET CATALOG.
Examples
On master database:
CREATE CATALOG INVENTORY; SET CATALOG INVENTORY; COMMIT WORK;
On replica database:
CREATE CATALOG INVENTORY SET CATALOG INVENTORY COMMIT WORK;
Notes
▪ A catalog name does not need to be the same in a master and replica database.
▪ You can specify catalogs by using fully-qualified table names (including the catalog name), or you can use the SET CATALOG statement to specify which catalog you want to use (if you do not specify a fully qualified name).
