SQLServer connector using incorrect columns for sorting changes [DBZ-8639]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-8639](https://issues.redhat.com/browse/DBZ-8639)
h2. What Debezium connector do you use and what version?
SQL Server version 2.7.3
h2. What behavior do you expect?
The [SQL Server docs|https://learn.microsoft.com/en-us/sql/relational-databases/system-tables/cdc-capture-instance-ct-transact-sql?view=sql-server-ver16] recommend that changes from the change table should be {{{}ORDER BY [__$start_lsn] ASC, [__$command_id] ASC, [__$operation] ASC{}}}.
h2. What behavior do you see?
The connector is ordering changes from the change table by {{ORDER BY [__$start_lsn] ASC, [__$seqval] ASC, [__$operation] ASC}}
This was originally raised as a [question on Zulip|https://debezium.zulipchat.com/#narrow/stream/348252-community-sqlserver/topic/Ordering.20of.20changes.20from.20SQL.20Server].
Contributor guide
Assessment
This issue has not been assessed yet.