Advanced Analytica Advanced Analytica: IBOM
← All connectors
Microsoft SQL Server (MSSQL) logo

Source connector

Microsoft SQL Server (MSSQL)

Set up Microsoft SQL Server (MSSQL) as a source and move its data into your chosen destination.

Version 5.1.5 certified alpha

Microsoft SQL Server (MSSQL)

Airbyte’s certified MSSQL connector gives you these features:

⚠️ Please note the minimum required platform version is v0.58.0 to run source-mssql 4.0.18 and above.

Features

FeatureSupportedNotes
Full Refresh SyncYes
Incremental Sync - AppendYes
Replicate Incremental DeletesYes
CDC (Change Data Capture)Yes
SSL SupportYes
SSH Tunnel ConnectionYes
Microsoft Entra ID AuthYesService principal
NamespacesYesEnabled by default

The MSSQL source doesn’t alter your database schema. However, the connected destination may alter it. See the destination’s documentation for details.

Get started

Requirements

  1. MSSQL Server Azure SQL Database, Azure Synapse Analytics, Azure SQL Managed Instance, SQL Server 2022, SQL Server 2019, SQL Server 2017, SQL Server 2016, SQL Server 2014, SQL Server 2012, PDW 2008R2 AU34.
  2. Create a dedicated, read-only Airbyte user with access to every table you need to replicate.
  3. To use CDC, review the relevant section below for further setup requirements.

1. Make your database accessible to Airbyte

Access depends on your network setup. Use the UI’s check connection tool to confirm Airbyte can connect to your MSSQL instance.

For Airbyte Cloud, your firewall or security group must allow the Airbyte Cloud IP addresses. The connection must also be encrypted. See Airbyte Cloud below.

This optional step gives you better permission control and auditing. Alternatively, you can connect Airbyte using an existing database user.

  • Create an Airbyte login and database user, then add the user to the db_datareader role. Membership in db_datareader grants SELECT on every current and future database table:

    USE {database name};
    CREATE LOGIN {user name} WITH PASSWORD = '{password}';
    CREATE USER {user name} FOR LOGIN {user name};
    ALTER ROLE db_datareader ADD MEMBER {user name};

    ALTER ROLE ... ADD MEMBER replaces the deprecated sp_addrolemember stored procedure, which Microsoft recommends avoiding in new work.

  • To limit access to specific schemas, skip the db_datareader role. Instead, grant SELECT on each schema you want to replicate. Run this command for every schema:

    USE {database name};
    GRANT SELECT ON SCHEMA :: {schema name} TO {user name};

Use this username and password when configuring the MSSQL source in Airbyte. For CDC, the user also needs permissions described in Setting up CDC for MSSQL.

3. Your database user is ready for Airbyte

Airbyte Cloud

Airbyte Cloud only supports secured connections to your MSSQL instance in the source configuration. It never connects to a database without encryption.

The connection must use TLS/SSL or an SSH tunnel. The tunnel encrypts the connection between Airbyte and your bastion host. In practice:

SetupSupported on Airbyte Cloud
Encryption set to Encrypted (trust server certificate) or Encrypted (verify certificate)Yes, with or without an SSH tunnel.
Encryption set to Unencrypted with an SSH tunnelYes. The SSH tunnel provides the encryption.
Encryption set to Unencrypted without an SSH tunnelNo. The connection test fails with Connection from Airbyte Cloud requires SSL encryption or an SSH tunnel.
Database on localhost or on a private network (not reachable from the public internet)Only through an SSH tunnel to a bastion host that can reach the database, which also provides the encryption Airbyte Cloud requires. With No Tunnel, localhost, 127.0.0.1 or 0.0.0.0 fails the connection test with Airbyte Cloud cannot reach a database on your own machine. Use a hostname reachable from the internet, or configure an SSH tunnel.
A URL, credentials or host:port pasted into HostNo. The connection test fails with Enter only the hostname in Host; put the port in the Port field. Enter only the hostname or IP address in Host and the port in Port.

On Airbyte Cloud, Encryption defaults to Encrypted (trust server certificate).

See Connection to MSSQL via an SSH Tunnel to set up the tunnel. If your network restricts inbound connections, see IP allow list.

Microsoft Entra ID authentication

This connector supports Microsoft Entra ID authentication, formerly Azure Active Directory, through a service principal. It’s an alternative to SQL Server username and password authentication.

This authentication mode is recommended for Azure SQL Database and Azure SQL Managed Instance.

Prerequisites

  1. An Azure SQL Database, Azure SQL Managed Instance or SQL Server instance configured for Microsoft Entra authentication. For setup instructions, see Configure and manage Microsoft Entra authentication with Azure SQL.
  2. A Microsoft Entra ID app registration (service principal) with a client secret.
  3. A database user created for the service principal, with SELECT access to the tables you want to replicate. For instructions, see Create Microsoft Entra users using service principals.
  4. For CDC, the service principal user also needs the CDC permissions described in Setting up CDC for MSSQL.

Configuration

Complete these fields under Microsoft Entra ID in the source configuration form:

FieldDescription
Entra ID Client IDThe application (client) ID of the service principal.
Entra ID Client SecretThe client secret generated for the service principal.

When you provide both fields, the connector authenticates in ActiveDirectoryServicePrincipal mode through the Microsoft JDBC driver. It ignores Username and Password.

If either Entra ID field is empty, the connector uses username and password authentication.

:::note Entra ID authentication requires an encrypted connection. Set Encryption to Encrypted (trust server certificate) or Encrypted (verify certificate).

The configuration check fails if you set Entra ID fields while encryption is disabled. :::

MSSQL replication modes

Incremental syncs

MSSQL datetime2(7) stores timestamps with up to seven decimal places. Most destinations don’t support this precision, so Airbyte truncates timestamps to six decimal places, or microseconds.

The saved cursor can therefore fall just behind your table’s newest rows. To prevent skipped rows, each incremental sync reads everything above the saved cursor.

It then saves the new maximum value as the cursor for the next sync.

:::note

Each sync collects everything newer than the last saved point, so you may see duplicate rows. Where supported, Incremental - Append + Deduped is recommended for these syncs.

For more information, see the Sync Mode page.

:::

Change Data Capture (CDC)

Airbyte uses SQL Server’s change data capture feature with transaction logs to capture row-level INSERT, UPDATE and DELETE operations on CDC-enabled tables.

Additional setup requires at least db_owner permissions on each database you intend to sync. See below for details.

Read CDC docs for an overview of Airbyte’s approach to CDC.

Should you use CDC for MSSQL?

  • Use CDC if you need deletion records and can accept the limitations below.
  • For a small dataset or destination snapshot, consider Full Refresh replication instead of CDC.
  • If CDC’s limitations prevent its use, consider non-CDC incremental replication to maintain a snapshot. Occasionally reset the data and sync again.
  • If your table has a primary key but no suitable incremental cursor, such as updated_at, CDC supports incremental syncing.

CDC limitations

  • Read CDC docs for limitations affecting every database that uses CDC replication.
  • hierarchyid and sql_variant types aren’t processed with the CDC migration type because Debezium doesn’t support them. For details, see this ticket.
  • CDC is only available for SQL Server 2016 Service Pack 1 (SP1) and later.
  • db_owner (or higher) permissions are required to perform the necessary setup for CDC.
  • On Linux, CDC isn’t supported before SQL Server 2017 CU18. SQL Server 2019 is supported.
  • You can’t enable change data capture on tables with a clustered columnstore index. You can enable it with a non-clustered columnstore index.
  • SQL Server CDC only processes changes in user-created tables. You can’t enable CDC on the SQL Server master database.
  • The ALTER TABLE … SWITCH TO … PARTITION … statement doesn’t support variables with partition switching on CDC-enabled databases or tables.
  • CDC incremental syncing only supports tables with at least one primary key. CDC can replicate tables without primary keys only in Full Refresh mode. For more information about CDC limitations, see CDC Limitations doc.
  • Airbyte’s CDC implementation provides at-least-once delivery for every change record.
  • Read more about CDC limitations in Microsoft docs.

Set up CDC for MSSQL

1. Enable CDC for the database and tables

MS SQL Server provides built-in stored procedures for enabling CDC.

  • First, a SQL Server administrator with db_owner or sysadmin privileges must enable CDC at the database level.

    USE {database name}
    GO
    EXEC sys.sp_cdc_enable_db
    GO
  • The administrator must then enable CDC for every table you want to capture. Here’s an example:

    USE {database name}
    GO
    
    EXEC sys.sp_cdc_enable_table
    @source_schema = N'{schema name}',
    @source_name   = N'{table name}',
    @role_name     = N'{role name}',  [1]
    @filegroup_name = N'{filegroup name}', [2]
    @supports_net_changes = 0 [3]
    GO
    • [1] Specifies a role that receives SELECT permission on the source table’s captured columns. Set a value so you can use this role in the next step. Alternatively, set @rolename to NULL. This restricts access to _sysadmin and db_owner. Ensure the Airbyte source credentials match this role, so Airbyte can access the cdc tables.
    • [2] Specifies the filegroup where SQL Server stores the change table. A separate CDC filegroup is recommended. You can omit this parameter to use the default filegroup.
    • [3] When set to 0, SQL Server only generates support functions for querying all changes. When set to 1, it also generates functions for querying net changes. If supports_net_changes is 1, specify index_name or ensure the source table has a defined primary key.
  • For more information about the parameters, see Microsoft doc page for this stored procedure.

  • If you need to enable CDC on many tables, use this script to avoid running this query separately for every table.

For more detail, see Microsoft docs on enabling and disabling CDC.

:::note Google Cloud SQL for SQL Server

On Google Cloud SQL for SQL Server, Google doesn’t grant customers the sysadmin server role. Therefore, you can’t run sys.sp_cdc_enable_db to enable database-level CDC.

Instead, use Cloud SQL’s dedicated stored procedure. It enables CDC without sysadmin:

EXEC msdb.dbo.gcloudsql_cdc_enable_db 'YOUR_DATABASE_NAME'

To disable database-level CDC later, use the corresponding EXEC msdb.dbo.gcloudsql_cdc_disable_db 'YOUR_DATABASE_NAME' procedure.

Only database-level enablement differs on Cloud SQL. Enabling CDC on individual tables still uses the standard sys.sp_cdc_enable_table procedure.

The snapshot isolation and user permission steps below remain unchanged. For Google’s complete procedure, see Configure CDC for a Cloud SQL for SQL Server source.

:::

2. Enable snapshot isolation
  • During the first CDC sync, Airbyte takes an initial, consistent database snapshot. Airbyte uses snapshot isolation to avoid table locks. This approach allows other database clients to write simultaneously. Enable it on the database as follows:

    ALTER DATABASE {database name}
      SET ALLOW_SNAPSHOT_ISOLATION ON;
3. Create a user and grant permissions
  • Create a new Airbyte user with the relevant CDC access instead of using sysadmin or db_owner credentials. First, create the login and user. Then add the user to the db_datareader role:

    USE {database name};
    CREATE LOGIN {user name} WITH PASSWORD = '{password}';
    CREATE USER {user name} FOR LOGIN {user name};
    ALTER ROLE db_datareader ADD MEMBER {user name};
    • Add the user to the role you specified when enabling cdc on the table(s):

      ALTER ROLE {role name} ADD MEMBER {user name};
    • ALTER ROLE ... ADD MEMBER replaces the deprecated sp_addrolemember stored procedure, which Microsoft recommends avoiding in new work.

    • This access should be sufficient. If you encounter problems, also grant the user direct SELECT access to the cdc schema:

      USE {database name};
      GRANT SELECT ON SCHEMA :: [cdc] TO {user name};
    • Where feasible, grant this user ‘VIEW SERVER STATE’ permissions. Airbyte can then check whether the SQL Server Agent is running. This is preferred because syncs fail if the Agent isn’t updating CDC tables in the source database.

      USE master;
      GRANT VIEW SERVER STATE TO {user name};
4. Extend CDC data retention
  • By default, SQL Server retains only three days of data in change tables. Increase retention unless you run very frequent syncs. Longer retention provides time to restart from the last incremental sync point after a failure or pause. Airbyte recommends retaining at least 7 days of CDC data.

  • Change these settings with the sys.sp_cdc_change_job stored procedure, as shown below:

    -- Airbyte recommends at least 10080 minutes (7 days) as the retention period
    EXEC sp_cdc_change_job @job_type='cleanup', @retention = 10080
  • After this change, restart the cleanup job:

  EXEC sys.sp_cdc_stop_job @job_type = 'cleanup';

  EXEC sys.sp_cdc_start_job @job_type = 'cleanup';
  • If you use Transaction Replication, change retention with these scripts:

EXEC sp_changedistributiondb
  @database = 'distribution',
  @property = 'max_distretention',
  @value = 10080 -- 10080 minutes (7 days)

EXEC sp_changedistributiondb
  @database = 'distribution',
  @property = 'history_retention',
  @value = 10080 -- 10080 minutes (7 days)

USE [msdb]
GO
EXEC msdb.dbo.sp_update_jobstep @job_name=N'Distribution clean up: distribution', @step_id=1 ,
		@command=N'EXEC dbo.sp_MSdistribution_cleanup @min_distretention = 0, @max_distretention = 10800'
GO
5. Ensure the SQL Server Agent is running
  • MSSQL uses the SQL Server Agent to run the jobs necessary for CDC. The Agent must run for CDC to work correctly. Check the SQL Server Agent’s status as follows:
  EXEC xp_servicecontrol 'QueryState', N'SQLServerAGENT';
  • If you see a status other than ‘Running.’, follow Microsoft docs to start the service.

Connect to MSSQL through an SSH tunnel

Airbyte can connect to an MSSQL instance through an SSH tunnel. Use a tunnel when direct database access is unavailable or violates security policy.

For example, the database may not have a public IP address.

An SSH tunnel connects Airbyte through an intermediate server, also called a bastion server. The bastion has direct database access.

Airbyte connects to the bastion, which then connects directly to the database server. Set the source’s Host and Port to the database address visible from the bastion.

For example, use localhost and 1433 when SQL Server runs on the bastion.

:::note Airbyte Cloud Airbyte Cloud never connects to a database without encryption. An SSH tunnel meets this requirement by encrypting the connection to the bastion.

On Airbyte Cloud, a tunnel is the only way to use the Unencrypted encryption method. It’s also required for databases on localhost or private networks.

Without a tunnel, Airbyte Cloud requires an encrypted SSL method. See Airbyte Cloud. :::

This feature needs additional source configuration. The following steps explain each configuration field.

  1. Configure every source field as usual, except SSH Tunnel Method.

  2. SSH Tunnel Method defaults to No Tunnel (a direct connection). To use an

    SSH tunnel, choose SSH Key Authentication or Password Authentication.

    1. Choose Key Authentication when using an RSA private key as your secret for

      establishing the SSH tunnel. See below for instructions on generating this key.

    2. Choose Password Authentication when using a password as your secret for establishing

      the SSH tunnel.

  3. SSH Tunnel Jump Server Host identifies the intermediate (bastion) server that Airbyte connects to. Enter

    a hostname or IP address.

  4. SSH Connection Port is the bastion server port used for the SSH connection. The default port for

    SSH connections is 22. Use this default unless you’ve explicitly changed the port.

  5. SSH Login Username is the username Airbyte uses to connect to the bastion server. It isn’t the

    MSSQL username.

  6. If you’re using Password Authentication, set SSH Login Username to the

    previous step’s user password. If you’re using SSH Key Authentication, leave this

    blank. This isn’t the MSSQL password. It’s the password for the operating system user that Airbyte uses

    to run commands on the bastion.

  7. If you’re using SSH Key Authentication, set SSH Private Key to the RSA

    private key used to create the SSH connection. Include the key file’s complete contents,

    starting with -----BEGIN RSA PRIVATE KEY----- and ending

    with -----END RSA PRIVATE KEY-----.

Generate an SSH key pair

The connector requires an RSA key in PEM format. Generate it as follows:

ssh-keygen -t rsa -m PEM -f myuser_rsa

This creates the private key in PEM format. The public key remains in the standard format used by the bastion host’s authorized_keys file.

Add the public key to the bastion host for the user you want Airbyte to use. Paste the private key into Airbyte’s connector configuration screen.

The connector can then log in to the bastion.

Data type mapping

MSSQL data types map to the following types during synchronisation. See the test value examples here.

If your required data type is missing or causes problems, you can add a new test.

MSSQL TypeResulting TypeNotes
bigintinteger
binarybinary
bitboolean
charstring
datedate
datetimetimestamp
datetime2timestamp
datetimeoffsettimestamp with timezone
decimalnumber / integermaps to integer when the column scale is 0
intinteger
floatnumber
geographystring
geometrystring
moneynumber
numericnumber / integermaps to integer when the column scale is 0
ntextstring
nvarcharstring
nvarchar(max)string
realnumber
smalldatetimetimestamp
smallintinteger
smallmoneynumber
sql_variantstring
uniqueidentifierstring
textstring
timetime
tinyintinteger
varbinarybinary
varcharstring
varchar(max) COLLATE Latin1_General_100_CI_AI_SC_UTF8string
hierarchyidstringNon-CDC only
xmlstring

If a type isn’t listed, assume it’s coerced into a string. Feedback on preferred mappings is welcome.

User-defined alias types

SQL Server supports alias types based on built-in types, such as CREATE TYPE alias_timestamp FROM datetime. The connector doesn’t map alias types by name.

Instead, it uses the column’s JDBC type reported by the SQL Server driver. This type comes from the alias’s base type.

The connector maps aliases over these base types like the base types themselves, including during CDC syncs:

Alias base typeJDBC typeResulting Type
dateDATEdate
timeTIMEtime
datetimeTIMESTAMPtimestamp
datetime2TIMESTAMPtimestamp
smalldatetimeTIMESTAMPtimestamp

Aliases over unlisted base types may cause mapping issues. Their JDBC types may not map like the built-in types.

Use built-in SQL Server types instead of alias types for columns you sync with Airbyte.

Upgrade to version 4.3.0 or later

Version 4.3.0 moves the connector from the legacy CDK to the new CDK architecture. This migration includes:

  • Automatic State Migration: The connector automatically migrates legacy version 2 state formats to the new version 3 format. This includes:
    • OrderedColumnLoadStatus (primary key-based initial sync) → version 3 primary_key state type
    • CursorBasedStatus (cursor-based incremental) → version 3 cursor_based state type
  • Backward Compatibility: Existing connections continue working without manual intervention.

Upgrade from 0.4.17 or earlier to 0.4.18 or later

Microsoft SQL Source connector versions 0.4.17 and 0.4.18 have a backwards-incompatible specification change.

The change updates the replication_method configuration parameter to object from string.

In Microsoft SQL source connector version 0.4.17 and earlier, the replication_method configuration parameter was saved in the configuration database as follows:

"replication_method": "STANDARD"

From version 0.4.18, the replication_method configuration parameter is saved as follows:

"replication_method": {
    "method": "STANDARD"
}

After upgrading from Microsoft SQL Source connector version 0.4.17 or earlier, fix the source configurations in Airbyte’s actor table.

You must run two SQL queries. Follow Airbyte documentation to run SQL queries on the Airbyte database.

For Microsoft SQL Source connections using the Standard replication method, run this SQL:

update public.actor set configuration =jsonb_set(configuration, '{replication_method}', '{"method": "STANDARD"}', true)
WHERE actor_definition_id ='b5ea17b1-f170-46dc-bc31-cc744ca984c1' AND (configuration->>'replication_method' = 'STANDARD');

For Microsoft SQL Source connections using the Logical Replication (CDC) method, run this SQL:

update public.actor set configuration =jsonb_set(configuration, '{replication_method}', '{"method": "CDC"}', true)
WHERE actor_definition_id ='b5ea17b1-f170-46dc-bc31-cc744ca984c1' AND (configuration->>'replication_method' = 'CDC');

IP allow list

If you use Airbyte Cloud and restrict access to specific IPs, add the Airbyte Cloud IP addresses to your allow list.

If Airbyte can’t open a TCP connection to your server, connection tests and syncs fail with:

SQL Server Connection Error: Airbyte could not reach SQL Server at the configured host and port.
Check the host and port, that the instance accepts remote TCP connections, and that your firewall
or security group allows Airbyte's IP addresses.

Possible causes include an incorrect host or port, an unresolved hostname or an instance that rejects remote TCP connections.

A firewall or security group may also block Airbyte Cloud IP addresses. Airbyte Cloud can’t reach databases on localhost or private networks without an SSH tunnel.

Before connecting, Airbyte Cloud rejects localhost with No Tunnel. It also rejects Airbyte Cloud cannot reach a database on your own machine. Use a hostname reachable from the internet, or configure an SSH tunnel. A URL or host:port pasted into Host with Enter only the hostname in Host; put the port in the Port field..

Changelog

Expand to review
VersionDatePull RequestSubject
5.1.52026-11-0989073Fix CDC sync failure for columns using user-defined alias types over date, time, datetime, datetime2, or smalldatetime.
5.1.42026-11-0273349Escape spaces and $ in Debezium message keys, and quote schema names in the Debezium schema include list.
5.1.32026-10-2189634Upgrade to Bulk CDK 1.2.3: fix critical CVEs in Apache MINA (mina-core 2.0.31), MINA SSHD 2.20.0 and BouncyCastle 1.86; Kafka 4.1.2, Jetty 12.0.40, plexus-utils 3.6.2.
5.1.22026-10-1985353Cold-start a stream when its saved state is an empty object or an unrecognized legacy format instead of skipping it.
5.1.12026-10-1288500Replace the sync-oriented retry wording of unreachable-host errors with guidance on the host, port, firewall, and Airbyte Cloud IP allow list; note that Unencrypted needs an SSH tunnel on Airbyte Cloud. Explain the Discovered zero tables. connection-test failure: say that no table is visible to the login and how to grant SELECT. On Airbyte Cloud, default the Encryption option to Encrypted (trust server certificate). On Airbyte Cloud, reject localhost without an SSH tunnel and a URL or host:port pasted into Host with an explicit message before the connection is attempted.
5.1.02026-10-1286318Add Debezium’s max_iteration_transactions (max.iteration.transactions) as an advanced CDC option, defaulting to 500.
5.0.22026-10-0988429Upgrade to Bulk CDK 1.1.14.
5.0.12026-09-0984356Change Debezium data.query.mode from direct to function to prevent syncs from hanging on large tables.
5.0.02026-06-2377672Map DECIMAL/NUMERIC columns with scale 0 to Airbyte integer instead of number so destinations preserve integral semantics.
4.4.122026-06-1780156Log a message when a DECIMAL/NUMERIC column with scale 0 is discovered, ahead of an upcoming number -> integer remapping. No functional change.
4.4.112026-06-1179128Fix incremental sync failure when the saved state has a null cursor (table was empty on prior CDK version).
4.4.102026-06-1079149Update cursor-based incremental query to prevent missing rows with high-precision datetime cursors.
4.4.92026-06-0277998Validate CDC access per configured stream to prevent zero-LSN errors caused by missing permissions.
4.4.82026-05-2678415Classify Azure read-replica error 3947 as transient so affected syncs retry instead of failing.
4.4.72026-05-1278033Re-release the Java connector base image revert after the 4.4.6 publish failure.
4.4.62026-05-0777856Revert the Java connector base image to resolve connection issues and remove registry rollback overrides.
4.4.52026-05-0777843Roll back source mssql to 4.4.3 to investigate a potential connection issue.
4.4.42026-05-0777665Fix sampling sync failure on empty tables in Full Refresh mode (NULL upper bound).
4.4.32026-05-0577786Make the hidden additional properties fields in spec optional. No functional change.
4.4.22026-04-2977036Fix TABLESAMPLE failure on views and tables without an ordered column in cursor-incremental syncs.
4.4.12026-04-2376857Fix Invalid column name error when sampling system-versioned temporal tables that have HIDDEN period columns.
4.4.02026-04-2376143Add Microsoft Entra ID service principal authentication for both JDBC and CDC paths.
4.3.62026-04-2074729Fix snapshot partitions restarting from the beginning of the table instead of resuming from the last checkpoint.
4.3.52026-02-2373606Fix CDC cursor overflow.
4.3.42026-02-1772935Update LSN validation to correctly detect when saved offset has been truncated.
4.3.32026-02-0371821Require a manual refresh when schema history is missing, bump CDK version.
4.3.22025-12-1170836Add Azure SQL Database compatibility for SQL Server Agent check
4.3.12025-12-0970823Bump up connector version number to release the connector
4.3.0-rc.102025-12-0570306Update CDK version to include fix for Debezium closing record race condition
4.3.0-rc.92025-12-0170280Fix connector concurrency default value
4.3.0-rc.82025-11-1469754Update to latest CDK version
4.3.0-rc.72025-11-1469327Change default schema to discover all schema instead of “dbo”
4.3.0-rc.62025-11-1269311Fix NPE in state migration when incremental_state is null; Reduce resourceAcquisitionHeartbeat to 100ms; Upgrade CDK version
4.3.0-rc.52025-11-0869248Add SQL Server identifier quoting to fix reserved keyword issues
4.3.0-rc.42025-11-0569194Fix composite primary key discovery to show all PK columns; separate PK discovery from sync strategy
4.3.0-rc.32025-10-3169097Fix connector state value type from string to json object
4.3.0-rc.22025-10-2969093Fix state parsing error for integer and number
4.3.0-rc.12025-10-2863731Migrate source mssql from old CDK to new CDK
4.2.62025-10-1468091Fix CDC table filtering to prevent unintended tables from being synced when using schema-level CDC
4.2.52025-08-1364905bumping up java cdk version for mssql
4.2.42025-07-0362491Improve Debezium performance by configuring the poll interval parameter.
4.2.32025-07-0162052Revert change to CDK interface signature.
4.2.22025-06-2561729Support the use of logical primary keys for CDC.
4.2.12025-06-2362015Fix previous merge. Improve cutoff date handling
4.2.02025-06-1961685Add an option to exclude today’s data from cursor based incremental syncs when using temporal cursor (datetime).
4.1.292025-06-0361320Add error handling for connection issues and adopt the latest CDK version.
4.1.282025-05-1560311Migrate to new gradle flow.
4.1.272025-04-2859124Fix _ab_cdc_event_serial_no datatype in addMetaDataToRowsFetchedOutsideDebezium method
4.1.262025-03-2756401Fix non-unique value clustered index issue
4.1.252025-03-2055878Integrate with the latest mssql jdbc driver to solve a pre-gregorian date offset bug
4.1.242025-03-1155709Filter unwanted tables in discover to prevent null table issues
4.1.232025-03-0655234Update base image version for certified DB source connectors
4.1.222025-02-1053217Default to PK when the clustered index is composite.
4.1.212025-02-2154189Print state data only in the debugging log.
4.1.202025-01-2652556Improve tables discovery during read.
4.1.192025-01-1651596Bump driver versions to latest (jdbc, debezium, cdk)
4.1.182025-01-0650943Use airbyte/java-connector-base:2.0.0. This makes the image rootless. The connector will be incompatible with Airbyte < 0.64.
4.1.172024-12-1749840Use a base image: airbyte/java-connector-base:1.0.0
4.1.162024-11-1348484Enhanced error handling for MSSQL to improve system error detection and response.
4.1.152024-10-0546515Improving discovery of large SQL server database.
4.1.142024-09-1745639Adopt latest CDK to use the latest apache sshd mina to handle tcpkeepalive requests.
4.1.132024-09-0545181Fix incorrect categorizing resumable/nonresumable full refresh streams.
4.1.122024-09-1045368Remove excessive debezium logging.
4.1.112024-09-0445142Fix incorrect datetimeoffset format in cursor state.
4.1.102024-08-2744759Improve null safety in parsing debezium change events.
4.1.92024-08-2744841Adopt latest CDK.
4.1.82024-08-0843410Adopt latest CDK.
4.1.72024-08-0642869Adopt latest CDK.
4.1.62024-07-3042550Correctly report stream states.
4.1.52024-07-2942852Bump CDK version to latest to use new bug fixes on error translation.
4.1.42024-07-2342421Remove final transient error emitter iterators.
4.1.32024-07-2242411Hide the “initial load timeout in hours” field by default in UI
4.1.22024-07-2242024Fix a NPE bug on resuming from a failed attempt.
4.1.12024-07-1942122Improve wass error message + logging.
4.1.02024-07-1742078WASS analytics + bug fixes.
4.0.362024-07-1741648Implement WASS.
4.0.352024-07-0540570Bump debezium-connector-sqlserver from 2.6.1.Final to 2.6.2.Final.
4.0.342024-07-0140516Remove dbz hearbeat.
4.0.332024-06-3040638Fix a bug that could slow down an initial load of a large table using a different clustered index from the primary key.
4.0.322024-06-2640558Handle DatetimeOffset correctly.
4.0.312024-06-1439419Handle DatetimeOffset correctly.
4.0.302024-06-1439349Full refresh stream sending internal count metadata.
4.0.292024-06-1439506Adopt latest CDK.
4.0.282024-06-0839342Fix custom conversion in CDC for datetimeoffset type.
4.0.272024-05-2938584Set is_resumable flag in discover.
4.0.262024-05-1638292Improve cursor value query to return only one row
4.0.252024-05-2938775Publish CDK
4.0.242024-05-2338640Sync sending trace status messages indicating progress.
4.0.232024-05-1538208disable counts in full refresh stream in state message.
4.0.222024-05-1438196Bump jdbc driver version to 12.6.1.jre11
4.0.212024-05-0738054Resumeable refresh should run only if there is source defined pk.
4.0.202024-05-0738042Bump debezium version to latest.
4.0.192024-05-0738029Fix previous release.
4.0.182024-04-3037451Resumable full refresh read of tables.
4.0.172024-05-0237781Adopt latest CDK.
4.0.162024-05-0137742Adopt latest CDK. Remove Debezium retries.
4.0.152024-04-2237541Adopt latest CDK. reduce excessive logs.
4.0.142024-04-2237476Adopt latest CDK.
4.0.132024-04-1637111Populate null values in record message.
4.0.122024-04-1537326Allow up to 60 minutes of wait for the an initial CDC record.
4.0.112024-04-1537325Populate airbyte_meta.changes + error handling.
4.0.102024-04-1537110Internal cleanup.
4.0.92024-04-1036919Fix a bug in conversion of null values.
4.0.82024-04-0536872Update to connector’s metadat definition.
4.0.72024-04-0336772Adopt latest CDK.
4.0.62024-03-2536333Deprecate Dbz state iterator.
4.0.52024-03-2136364Allow up to 40 minutes of wait for the an initial CDC record.
4.0.42024-03-2036325[Refactor] : Remove mssql initial source operations .
4.0.32024-03-1936263Fix a failure seen in CDC with tables containing default values.
4.0.22024-03-0635792Initial sync will now send record count in state message.
4.0.12024-03-1236011Read correctly null values of columns with default value in CDC.
4.0.02024-03-0635873Terabyte-sized tables support, reliability improvements, bug fixes.
3.7.72024-03-0635816Fix query that was failing on a case sensitive server.
3.7.62024-03-0435721Fix tests
3.7.52024-02-2935739Allow configuring the queue size used for cdc events.
3.7.42024-02-2635566Add config to throw an error on invalid CDC position.
3.7.32024-02-2335596Fix a logger issue
3.7.22024-02-2135368Change query syntax to make it compatible with Azure SQL Managed Instance.
3.7.12024-02-2035405Change query syntax to make it compatible with Azure Synapse.
3.7.02024-01-3033311Source mssql with checkpointing initial sync.
3.6.12024-01-2634573Adopt CDK v0.16.0.
3.6.02024-01-1033700Remove CDC config options for data_to_sync and snapshot isolation.
3.5.12024-01-0533510Test-only changes.
3.5.02023-12-1933071Fix SSL configuration parameters
3.4.12024-01-0233755Encode binary to base64 format
3.4.02023-12-1933481Remove LEGACY state flag
3.3.22023-12-1433505Using the released CDK.
3.3.12023-12-1233225extracting MsSql specific files out of the CDK.
3.3.02023-12-1233018Migrate to Per-stream/Global states and away from Legacy states
3.2.12023-12-1133330Parse DatetimeOffset fields with the correct format when used as cursor
3.2.02023-12-0733225CDC : Enable compression of schema history blob in state.
3.1.02023-11-2832882Enforce SSL on Airbyte Cloud.
3.0.22023-11-2732573Format Datetime and Datetime2 datatypes to 6-digit microsecond precision
3.0.12023-11-2232656Adopt java CDK version 0.5.0.
3.0.02023-11-0731531Remapped date, smalldatetime, datetime2, time, and datetimeoffset datatype to their correct Airbyte types
2.0.42023-11-06#32193Adopt java CDK version 0.4.1.
2.0.32023-10-3132024Upgrade to Debezium version 2.4.0.
2.0.22023-10-3031960Adopt java CDK version 0.2.0.
2.0.12023-08-2429821Set replication_method display_type to radio, update titles and descriptions, and make CDC the default choice
2.0.02023-08-2229493Set a default cursor for Cdc mode
1.1.12023-07-2428545Support Read Committed snapshot isolation level
1.1.02023-06-2627737License Update: Elv2
1.0.192023-06-2027212Fix silent exception swallowing in StreamingJdbcDatabase
1.0.182023-06-1427335Remove noisy debug logs
1.0.172023-05-2526473CDC : Limit queue size
1.0.162023-05-0125740Disable index logging
1.0.152023-04-2625401CDC : Upgrade Debezium to version 2.2.0
1.0.142023-04-1925345Logging : Log database indexes per stream
1.0.132023-04-1924582CDC : refactor for performance improvement
1.0.122023-04-1725220Logging changes : Log additional metadata & clean up noisy logs
1.0.112023-04-1124656CDC minor refactor
1.0.102023-04-0624820Fix data loss bug during an initial failed non-CDC incremental sync
1.0.92023-04-0424833Fix Debezium retry policy configuration
1.0.82023-03-2824166Fix InterruptedException bug during Debezium shutdown
1.0.72023-03-2724373Preparing the connector for CDC checkpointing
1.0.62023-03-2220760Removed redundant date-time datatypes formatting
1.0.52023-03-2124207Fix incorrect schema change warning in CDC mode
1.0.42023-03-2124275Fix error with CDC checkpointing
1.0.32023-03-1524082Fixed NPE during cursor values validation
1.0.22023-03-1423908Log warning on null cursor values
1.0.12023-03-1023939For network isolation, source connector accepts a list of hosts it is allowed to connect
1.0.02023-03-0623112Upgrade Debezium version to 2.1.2
0.4.292023-02-2416798Add event_serial_no to cdc metadata
0.4.282023-01-1821348Fix error introduced in 18959 in which option initial_waiting_seconds was removed
0.4.272022-12-1420346Consolidate date/time values mapping for JDBC sources
0.4.262022-12-1218959CDC : Don’t timeout if snapshot is not complete.
0.4.252022-11-0418732Upgrade debezium version to 1.9.6
0.4.242022-10-2518383Better SSH error handling + messages
0.4.232022-10-2118263Fixes bug introduced in 15833 and adds better error messaging for SSH tunnel in Destinations
0.4.222022-10-1918087Better error messaging for configuration errors (SSH configs, choosing an invalid cursor)
0.4.212022-10-1718041Fixes bug introduced 2022-09-12 with SshTunnel, handles iterator exception properly
2022-10-1315535Update incremental query to avoid data missing when new data is inserted at the same time as a sync starts under non-CDC incremental mode
0.4.202022-09-1415668Wrap logs in AirbyteLogMessage
0.4.192022-09-0516002Added ability to specify schemas for discovery during setting connector up
0.4.182022-09-0314910Standardize spec for CDC replication. Replace the replication_method enum with a config object with a method enum field.
0.4.172022-09-0116261Emit state messages more frequently
0.4.162022-08-1814356DB Sources: only show a table can sync incrementally if at least one column can be used as a cursor field
0.4.152022-08-1115538Allow additional properties in db stream state
0.4.142022-08-1015430fixed a bug on handling special character on database name
0.4.132022-08-0415268Added [] enclosing to escape special character in the database name
0.4.122022-08-0214801Fix multiple log bindings
0.4.112022-07-2214714Clarified error message when invalid cursor column selected
0.4.102022-07-1414574Removed additionalProperties:false from JDBC source connectors
0.4.92022-07-0514379Aligned Normal and CDC migration + added some fixes for datatypes processing
0.4.82022-06-2414121Omit using ‘USE’ keyword on Azure SQL with CDC
0.4.52022-06-2314077Use the new state management
0.4.32022-06-1713887Increase version to include changes from 13854
0.4.22022-06-0613435Adjust JDBC fetch size based on max memory and max row size
0.4.12022-05-2513419Correct enum for Standard method.
0.4.02022-05-2512759 13168For CDC, Add option to ignore existing data and only sync new changes from the database.
0.3.222022-04-2912480Query tables with adaptive fetch size to optimize JDBC memory consumption
0.3.212022-04-1111729Bump mina-sshd from 2.7.0 to 2.8.0
0.3.192022-03-3111495Adds Support to Chinese MSSQL Server Agent
0.3.182022-03-2911010Adds JDBC Params
0.3.172022-02-2110242Fixed cursor for old connectors that use non-microsecond format. Now connectors work with both formats
0.3.162022-02-1810242Updated timestamp transformation with microseconds
0.3.152022-02-1410256Add -XX:+ExitOnOutOfMemoryError JVM option
0.3.142022-01-249554Allow handling of java sql date in CDC
0.3.132022-01-079094Added support for missed data types
0.3.122021-12-309206Update connector fields title/description
0.3.112021-12-248958Add support for JdbcType.ARRAY
0.3.102021-12-018371Fixed incorrect handling “\n” in ssh key
0.3.92021-11-097748Improve support for binary and varbinary data types
0.3.82021-10-267386Fixed data type (smalldatetime, smallmoney) conversion from mssql source
0.3.72021-09-306585Improved SSH Tunnel key generation steps
0.3.62021-09-176318Added option to connect to DB via SSH
0.3.42021-08-134699Added json config validator
0.3.32021-07-054689Add CDC support
0.3.22021-06-093973Add AIRBYTE_ENTRYPOINT for Kubernetes support
0.3.12021-06-083893Enable SSL connection
0.3.02021-04-212990Support namespaces
0.2.32021-03-282600Add NCHAR and NVCHAR support to DB and cursor type casting
0.2.22021-03-262460Destination supports destination sync mode
0.2.12021-03-182488Sources support primary keys
0.2.02021-03-092238Protocol allows future/unknown properties
0.1.112021-02-021887Migrate AbstractJdbcSource to use iterators
0.1.102021-01-251746Fix NPE in State Decorator
0.1.92021-01-191724Fix JdbcSource handling of tables with same names in different schemas
0.1.92021-01-141655Fix JdbcSource OOM
0.1.82021-01-131588Handle invalid numeric values in JDBC source
0.1.62020-12-091172Support incremental sync
0.1.52020-11-301038Change JDBC sources to discover more than standard schemas
0.1.42020-11-301046Add connectors using an index YAML file
Advanced Analytica

Most businesses are sitting on information they can’t use at speed. The people who hold it are busy, and when they leave, the knowledge goes with them. The documents are static, and the processes around them weren’t designed for AI.

Advanced Analytica works with these businesses to turn that information into structured data assets. Once they're integrated, AI systems can govern it, and the business can use it. We bring in the strategy, the specification and the AI skills to rework how the business operates.

MOVE FAST. STAY SAFE.