In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

1.4 
SQLServer connector

What is the connector configuration?

Default

What is the captured database version and mode of depoyment?

On-prem, SQL Server 2016

What behaviour do you expect?

Be able to handle tables with high throughput

What behaviour do you see?

Tables with low throughput are ok. But tables with high throughput enabling CDC causes high latencies affecting production.

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

This is not a problem in Debezium itself. Simply enabling CDC on the SQL server manifests the problem

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

N/A

How to reproduce the issue using our tutorial deployment?

Enable CDC on a high traffic table

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Are there ways of tailing the transaction log (t-log) that would produce the same information in the connector, while placing less load on the server? What idea have you explored so far and what's a good direction to take here?

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>