Striim 4.0.4 documentation

SQL Server

MS SQL Reader supports:

  • SQL Server Enterprise versions 2008, 2012, 2014, 2016, and 2017

  • SQL Server Standard versions 2016 and 2017

  • Azure SQL Database managed instances

Since Azure SQL Database single databases and elastic pools do not support change data capture (see Azure SQL Database Features), use Incremental Batch Reader or Database Reader to read from them.Incremental Batch ReaderDatabase Reader

Striim provides templates for creating applications that read from SQL Server and write to various targets. See Creating an application using a template for details.

MSJet reads logical changes directly from SQL Server's transaction logs. Unlike MS SQL Reader, MSJet does not require SQL Server's CDC change tables, and CDC is automatically enabled on a per-table basis.

MSJet supports Microsoft SQL Server versions 2016 (SP2), 2017, and 2019 running on 64-bit Windows 10 or Windows Server 2012 or later. It is not compatible with SQL Server running on other operating systems or on Windows on ARM.

MSJet must be deployed on a Forwarding Agent on the SQL Server system on a Striim cluster running on 64-bit Windows 10 or Windows Server 2012 or later (Windows on ARM is not supported).

Microsoft Visual C++ 2015-2019 Redistributable (x64) version 14.28.29914 or later (see Visual Studio 2015, 2017, 2019, and 2022) must be installed in the Windows environment where MSJet is deployed..

MSJet limitations in this release:

  • Each Striim server or Forwarding Agent can run only a single MSJet source. If you need multiple MSJet sources, deploy each on a different server or Forwarding Agent.

  • Page compression is supported but not row compression.

  • Tables with XML columns are not supported.

  • Reading from secondary databases is not supported.

  • Reading from backups is supported only if they are accessible only in the location where they were taken.

  • Debug messages for the Wiindows-native portion of the adapter may appear in striim/logs/striim_mssqlnativereader.log rather than in cstriim.server.log.