Bug report

What Debezium connector do you use and what version?

SQL Server connector. Issue observed in Debezium versions:

• 2.2.1.Final (in production environemnt)
• 2.4.1.Final (reproduced in QA environment)
• 2.5.0.Final (used to create integration test case demonstrating issue, which is attached to this issue).

What is the connector configuration?

We use Debezium Server at multiple sites connected to SQL Server instances and writing to Azure Event Hubs. 
Have been able to reproduce issue by extending Debezium's integration tests, so occurs with default configuration used for these tests.

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

SQL Server 2019, on-premise at multiple sites. Dedicated debezium server per site.

What behaviour do you expect?

That all records from a table should be sent when a full incremental snapshot is submitted (i.e. no additional conditions included). 

What behaviour do you see?

In this particular instance a block of 36 records were skipped from a total of 11499.

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

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

Yes (see attached test case, which is a modified version SQLServer's
IncrementalSnapshotIT). I believe this issue exists in the latest source base.

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

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

No.

How to reproduce the issue using our tutorial deployment?

see attached test case.