Skip to main content

Striim Cloud 4.1.0 documentation

MSJet properties


Before you can use this adapter, the tasks described in SQL Server setup for MSJet must be completed.

MSJet must be deployed to a Forwarding Agent (or Striim server) running on the same Windows system as the SQL Server instance that hosts the databases to be read.

If the adapter is deployed to a Forwarding Agent, the Microsoft JDBC driver must be installed as described in Install the Microsoft JDBC Driver in a Forwarding Agent.

This adapter has the following properties:



default value


Bidirectional Marker Table


When performing bidirectional replication, the fully qualified name of the marker table (see Bidirectional replication). This setting is case-sensitive.

CDDL Action



See Handling schema evolution.

CDDL Capture



See Handling schema evolution.

Committed Transactions



By default, only committed transactions are read. Set to False to read both committed and uncommitted transactions.




Set to True when the output of the source is the input of a DatabaseWriter target that writes to Cassandra {see Cassandra Writer).

Connection Retry Policy


timeOut=30, retryInterval=30, maxRetries=3

With the default setting:

  • Striim will wait for the database to respond to a connection request for 30 seconds (timeOut=30).

  • If the request times out, Striim will try again in 30 seconds (retryInterval=30).

  • If the request times out on the third retry (maxRetries=3), a ConnectionException will be logged and the application will stop.

Negative values are not supported.

Connection URL


IP address and port of Microsoft SQL server, separated by a colon: for example, If reading from a secondary database in an Always On availability group, use <IP address>:<port>;applicationIntent=ReadOnly.

MSJet supports TLS 1.2 (see Transport Layer Security (TLS)). No configuration is required on Striim's side.

If the connection requires SSL, see Set up connection to MSSQLReader with SSL in Striim's knowledge base.

Database Name


the SQL Server database name

Excluded Tables


If the Tables string contains wildcards, any tables specified here will be excluded.

Filter Transaction Boundaries



With the default value of True, begin and commit transactions are filtered out. Set to False to include begin and commit transactions.

Integrated Security



When set to the default value of False, the adapter will use SQL Server Authentication. Set to True to use Windows Authentication, in which case the adapter will authenticate as the user running the Forwarding Agent or Striim server on which it is deployed, and any settings in Username or Password will be ignored. See Choose an Authentication Mode for more information.


encrypted password

The password specified for the username (see Encrypted passwords).

Quiesce Marker Table



See Creating the QUIESCEMARKER table for MSJet. Modify the default value if the quiesce marker table is not in the schema associated with the user specified in the Username.

Send Before Image



set to False to omit before data from output

Start Position



With the default value EOF, reading starts at the end of the log file (that is, only new data is read). Alternatively, you may specify a specific time (in the Transact-SQL format TIME: YYYY-MM-DD hh:mm:ss:nnn, for example, TIME:2014-10-03 13:32:32.917) or SQL Server log sequence number (for example, LSN:0x00000A85000001B8002D) for the Begin operation of the transaction from which to start reading.

See also Switching from initial load to continuous replication.



The table(s) or view(s) in for which to return change data. Names must be specified as <schema name>.<table name> and are case-sensitive. (The server is specified by the IP address in connectionURL and the database by databaseName.)

You may specify multiple tables and views as a list separated by semicolons or with the following wildcards:

  • %: any series of characters

  • _: any single character

For example, my.% would read all tables in the my schema. At least one table must match the wildcard or start will fail with a "Could not find tables specified in the database" error. Temporary tables (which start with #) are ignored.

Transaction Buffer Spillover Size



When Transaction Buffer Type is Memory, this setting has no effect.

When Transaction Buffer Type is Disk, the amount of memory that Striim will use to hold each in-process transactions before buffering it to disk. You may specify the size in MB or GB.

Transaction Buffer Type



When Striim runs out of available Java heap space, the application will crash. Typically this will happen when a transaction includes millions of INSERT, UPDATE, or DELETE events with a single COMMIT.

To avoid this problem, with the default setting of Disk, when a transaction exceeds the Transaction Buffer Spillover Size, Striim will buffer it to disk at the location specified by the Transaction Buffer Disk Location property, then process it when memory is available.

When the setting is Disk and recovery is enabled (see Recovering applications), after the application crashes or is stopped the buffer will be reset, and during recovery any previously buffered transactions will restart from the beginning.Recovering applications

To disable transaction buffering, set Transaction Buffer Type to Memory.



If Integrated Security is True, leave blank. If Integrated Security is False, specify the login name for the SQL Server user.