View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006584 | SymmetricDS Pro | Improvement | public | 2024-09-11 18:34 | 2024-09-18 17:41 |
| Reporter | madcode | Assigned To | |||
| Priority | low | ||||
| Status | new | Resolution | open | ||
| Summary | 0006584: SYM_CONSOLE_TABLE_STATS: Capture name of table's catalog and schema | ||||
| Description | Currently, number of changed rows gets captured (about every 5 minutes) and saved in the SYM_CONSOLE_TABLE_STATS table. Captured data does not contain catalog and schema names, though. This presents a challenge with disaggregating row counts for identically named tables in different catalogs or schemas. | ||||
| Steps To Reproduce | Central node collecting data from multiple clients into a single database with separate catalog (or schema) per client. 100 rows from table some_events from ClientA gets synced to ClientA.some_events table on the central node. During the same 5 minutes, another 200 rows from table some_events from ClientB gets synced to ClientB.some_events table on the central node. There will be only one record in the SYM_CONSOLE_TABLE_STATS with a total of 300 rows (LOADED_ROWS column) for the table some_events. | ||||
| Additional Information | Having this level of details will also be very helpful for SymmetricDSPro customers to quickly identify tables with large number of changes, which push prospective customer over the limit set by their temporary evaluation license. Displaying this information on the Support screen (for License Lock-out) would increase transparency and, potentially, lead to changes in configuration (skipping tables with local transitory data, like cache, which do not add value). Another helpful benefit would be ability to quickly identify which client system generates massive amount of changes for a given table. | ||||
| Tags | monitoring, statistics | ||||