Striim 3.9.7 documentation

Creating the checkpoint table

When recovery is not enabled, there is no need to create the checkpoint table.

When recovery is enabled, DatabaseWriter uses the table specified by the CheckpointTable property to store information used to ensure that there are no missing or duplicate events after recovery (see Recovering applications). Before starting DatabaseWriter with recovery enabled, use the following DDL to create the table, and grant insert, update, and delete privileges to the user specified in the Username property. The table and column names are case-sensitive, do not change them.

Cassandra or Cosmos DB:

CREATE TABLE chkpoint (
  id varchar PRIMARY KEY,
  sourceposition blob,
  pendingddl int,
  ddl ascii);

HP NonStop SQL/MX (replace <catalog>.<schema> with the catalog and schema in which to create the table):

CREATE TABLE <catalog>.<schema>.CHKPOINT (
  ID VARCHAR(100) NOT NULL NOT DROPPABLE PRIMARY KEY,
  SOURCEPOSITION VARCHAR(30400),
  PENDINGDDL NUMERIC(1),
  DDL VARCHAR(2000)
) ATTRIBUTES BLOCKSIZE 32768;

Microsoft SQL Server:

CREATE TABLE CHKPOINT (
  id VARCHAR(100) PRIMARY KEY,
  sourceposition VARBINARY(MAX), 
  pendingddl BIT, 
  ddl VARCHAR(MAX));

MySQL:

CREATE TABLE CHKPOINT (
  id VARCHAR(100) PRIMARY KEY, 
  sourceposition BLOB, 
  pendingddl BIT(1), 
  ddl LONGTEXT);

Oracle:

CREATE TABLE CHKPOINT (
  ID VARCHAR2(100) PRIMARY KEY, 
  SOURCEPOSITION BLOB, 
  PENDINGDDL NUMBER(1), 
  DDL CLOB);

PostgreSQL:

create table chkpoint (
  id character varying(100) primary key,
  sourceposition bytea,
  pendingddl numeric(1), 
  ddl text);