View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006816 | SymmetricDS Pro | Bug | public | 2025-04-11 15:26 | 2025-04-11 19:55 |
| Reporter | elong | Assigned To | elong | ||
| Priority | normal | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.13.0 | ||||
| Target Version | 3.15.16 | Fixed in Version | 3.15.16 | ||
| Summary | 0006816: SQL Server change tracking can replicate data twice or in different order | ||||
| Description | SQL Server log miner using change tracking can replicate data twice or in a different order, causing unnecessary fallback operations and potential foreign key errors. The automatic resolution of errors corrects the data and keeps it in sync, but it can slow down replication performance. The log miner is watching for changes up through the current change version, which may still have uncommitted transactions. Instead, log miner should watch for changes up through current change version minus one. If no changes are found, it can check for changes on the current version. If the same count of changes are waiting on a second check, then it can mine the current version. | ||||
| Tags | dialect: sql-server, log miner | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-04-11 15:26 | elong | New Issue | |
| 2025-04-11 15:26 | elong | Status | new => assigned |
| 2025-04-11 15:26 | elong | Assigned To | => elong |
| 2025-04-11 15:26 | elong | Tag Attached: dialect: sql-server | |
| 2025-04-11 15:26 | elong | Tag Attached: log miner | |
| 2025-04-11 17:23 | elong | Project | SymmetricDS => SymmetricDS Pro |
| 2025-04-11 19:47 | elong | Status | assigned => resolved |
| 2025-04-11 19:47 | elong | Resolution | open => fixed |
| 2025-04-11 19:47 | elong | Fixed in Version | => 3.15.16 |
| 2025-04-11 19:55 | elong | Issue cloned: 0006817 | |
| 2025-04-11 19:55 | elong | Relationship added | related to 0006817 |