MICROSOFT SQL SERVER SOURCE
Important
This connector is no longer available or supported by Confluent. Please use the SQL Server Source Connector.
To use this connector, specify the name of the connector class in the connector.class configuration property.
connector.class
connector.class=io.confluent.connect.cdc.mssql.MsSqlSourceConnector
Connector-specific configuration properties are described below.
initial.database
The initial database to connect to.
password
JDBC Password to connect to the database with.
server.name
The database server to connect to.
server.port
The port on the database server to connect to.
username
JDBC Username to connect to the database with.
change.tracking.tables
The tables in the source database to monitor for changes. If no tables are specified the [sys].[change_tracking_tables] view is queried for all of the available tables with change tracking enabled.
[sys].[change_tracking_tables]
jdbc.pool.max.idle
The maximum number of idle connections in the connection pool.
jdbc.pool.max.total
The maximum number of connections for the connection pool to open. If a number greater than this value is requested, the caller will block waiting for a connection to be returned. This setting is shared across all of the tasks for a given database.
jdbc.pool.min.idle
The minimum number of idle connections in the connection pool.
instance.name
The instance name for the SQL Server we are connecting to.
multi.subnet.failover.enabled
Flag to enable the multisubnet failover option.
schema.key.name.format
Format used to generate the name for the key schema. The following template variables are available for string replacement. ${databaseName}, ${schemaName}, ${tableName}, ${namespace}
${databaseName}
${schemaName}
${tableName}
${namespace}
schema.namespace.format
The namespace for the schemas generated by the connector. The format in this setting will be used to create the ${namespace}variable which is available for use in the other configuration templates. The following template variables are available for string replacement. ${databaseName}, ${schemaName}, ${tableName}, ${namespace}
schema.value.name.format
Format used to generate the name for the value schema. The following template variables are available for string replacement. ${databaseName}, ${schemaName}, ${tableName}, ${namespace}
schema.cache.ms
The number of milliseconds to cache key and value schema metadata in memory.
schema.caseformat.column.name
This setting is used to control how the column names are cased when the resulting schemas are generated.
LOWER_HYPHEN
LOWER_UNDERSCORE
LOWER_CAMEL
LOWER
UPPER_CAMEL
UPPER_UNDERSCORE
UPPER
NONE
schema.caseformat.database.name
This setting is used to control how the ${databaseName} variable is cased when it is passed to the formatters defined in the schema.namespace.format, schema.key.name.format, schema.value.name.format, topicFormat.format settings. This allows you to control the naming applied to these properties. For example this can be used to take a database name of USER_TRACKING to a more java like case of userTracking or all lowercase usertracking.
topicFormat.format
USER_TRACKING
userTracking
usertracking
schema.caseformat.input
The naming convention used by the database format. This is used to define the source naming convention used by the other schema.caseformat.* properties.
schema.caseformat.*
schema.caseformat.schema.name
This setting is used to control how the ${schemaName} variable is cased when it is passed to the formatters defined in the schema.namespace.format, schema.key.name.format, schema.value.name.format, topicFormat.format settings. This allows you to control the naming applied to these properties. For example this can be used to take a schema name of SCOTT to a more java like case of Scott or all lowercase scott.
SCOTT
Scott
scott
schema.caseformat.table.name
This setting is used to control how the ${tableName} variable is cased when it is passed to the formatters defined in the schema.namespace.format, schema.key.name.format, schema.value.name.format, topicFormat.format settings. This allows you to control the naming applied to these properties. For example this can be used to take a table name of USER_SETTING to a more java like case of UserSetting or all lowercase usersetting.
USER_SETTING
UserSetting
backoff.time.ms
The number of milliseconds to backoff when no records are returned from the source database.
The format that will be used to build the topic name. This allows database tables to be broken up across several topics. The following template variables can be used for string replacements. ${databaseName}, ${schemaName}, ${tableName}, ${namespace}
batch.size
The target number of records to return during each poll from the Connect framework. This setting is independent from the general producer setting batch.size
uncomitted.record.max
The maximum number of records to allow in memory. Once this limit is reached the record deque will block to prevent running out of memory.
uncomitted.record.timeout.ms
The maximum amount of time to wait when writing to the deque before throwing a timeout exception.