@kapa.ai are faster syncs coming to mssql to GBQ?

Thinking completed The knowledge sources do not explicitly mention a timeline or specific roadmap for when the platform-level "faster sync speed" feature will be enabled for the MSSQL source connector. Here is what the documentation currently confirms: • Requirements for faster sync speed: A connection can only use Airbyte's faster sync speed (which offers 4–10x improvements using direct socket-based IPC) if both the source and destination connectors support it, and if you are using Airbyte Cloud or Self-Managed version 1.8+ [Faster sync speed]. • Current connector support: ◦ Destination BigQuery already supports the faster sync speed feature [Faster sync speed; feat(destination-mssql): add connectorIPCOptions to enable speed mode]. ◦ However, for sources, only MySQL is currently listed as supporting faster sync speed [Faster sync speed]. Airbyte is continuously rolling out faster sync support to additional connectors over time [Faster sync speed], but there is no specific confirmation yet on when

source-mssql

will be included. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai carefully examine if mssql source has it

Thinking completed Based on a careful examination of the connector code and configuration in the knowledge sources, the MSSQL source connector (

source-mssql

) does already have the technical prerequisites for faster sync speed (speed mode) implemented at the connector level: 1. Declared IPC Support in Metadata: The connector definition for

source-mssql

includes the necessary

connectorIPCOptions

block enabling socket-based data transfer [Airbyte metadata.yaml]connectorIPCOptions dataChannel: version: "0.0.2" supportedSerialization: ["JSONL", "PROTOBUF"] supportedTransport: ["SOCKET", "STDIO"] 2. Socket Transport / Concurrency Handling in Code: The configuration code specifically accounts for running in "speed mode" over Unix domain sockets rather than legacy STDIO [MsSqlServerSourceConfiguration.kt]:// If maxConcurrency is set, we use it. // Otherwise, we use the number of socket paths provided for speed mode // Or 1 for legacy mode maxConcurrency = when (DataChannelMedium.valueOf(dataChannelMedium)) { DataChannelMedium.STDIO -> maxConcurrency ?: 1 DataChannelMedium.SOCKET -> maxConcurrency ?: socketPaths.size } Status for MSSQL to BigQuery • Connector readiness: Both

source-mssql

and destination BigQuery support the

SOCKET

transport IPC options [Airbyte metadata.yaml; feat(destination-mssql): add connectorIPCOptions to enable speed mode]. • Documentation status: The user-facing documentation page for "Faster sync speed" currently lists only MySQL under its officially supported sources [Faster sync speed]. The knowledge sources do not explicitly state whether the platform has fully activated/rolled out faster sync speed for MSSQL connections across all Cloud or Self-Managed environments yet, but the underlying connector-side implementation for speed mode is in place [Airbyte metadata.yaml; MsSqlServerSourceConfiguration.kt]. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.