Connect CDC SQData

Parsing and Starting the Engine is a two step process each consisting of a single command that can be run at the command line or more frequently using  two separate batch scripts.

The SQData Parser (SQDPARSE) creates a parsed Apply Engine script from a source script file.

Syntax

SQDPARSE  <engine>.sqd  <engine>.prc [LIST=ALL|SCRIPT] [ <parm1>  <parm2> …<parmn>] [>  <engine>.rpt]

 

Example

A batch script containing a single line similar to the following is frequently used to execute the parser:

sqdparse ./ENGINE/SQLTOSQL.sqd ./ENGINE/SQLTOSQL.prc ENGINE=SQLTOSQL HOST=winsvr1 PORT=2626 > ./ENGINE/SQLTOSQL.rpt

 

Note: In the Parser example the working directory is one level up from the directory containing the actual engine script, "ENGINE". References in the script to the location of SQL Server DDL table descriptions, called procedures, etc must be sensitive to their location in the directory hierarchy, ie: ./<directory_name>/<file_name>. In this case probably ./MSQLDDL (note the single dot).

 

The SQData Engine (SQDATA) uses the parsed Apply Engine script. The engine can be either executed directly at the command line or using a batch script or started using the Daemon.

 

Syntax

SQDATA <engine>.prc > <engine>.out

 

or using the sqdmon start command along with a properly configured daemon:

SQDMON start ///<engine_alias> --service=2626

 

Example

A simple batch script is frequently used to execute the engine:

sqdata ./ENGINE/SQLTOSQL.prc > SQLTOSQL.out

 

or using the sqdmon start command;

sqdmon start ///SQLTOSQL --service=2626

 

along with a properly configured sqdaemon:

[SQLTOSQL]

type=engine

program=sqdata

args=./ENGINE/SQLTOSQL.prc

working_directory=c:/sqdata/demo

stdout_file=/SQLTOSQL.out

stderr_file=/SQLTOSQL.out

auto_start=no

 

Note: In the Engine example the working directory, c:/sqdata/demo is one level up from the directory containing the actual engine script, "ENGINE". References to the parsed script must be to the location of parsed script.