View Revisions: Issue #6811
| Summary | 0006811: Exclude history tables generated by MS SQL Server for change capture and audit | ||
|---|---|---|---|
| Revision | 2025-04-09 16:49 by pbelov | ||
| Description | History tables are generated by MS SQL Server for change capture and audit. They are not "real" tables and should be excluded from: * New table trigger wizard. * Add tables to replication on Canvas. * Explorer tables tree view. It will also be helpful to have a parameter to turn off this filter, in a rare case customer actually needs access to all history tables. See also: https://dataedo.com/kb/query/sql-server/list-temporal-tables-in-database https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables?view=sql-server-ver16 |
||
| Revision | 2025-07-02 14:44 by awebb | ||
| Description | History tables are generated by MS SQL Server for change capture and audit. They are not "real" tables and should be excluded from: * New table trigger wizard. * Add tables to replication on Canvas. * Explorer tables tree view. It will also be helpful to have a parameter to turn off this filter, in a rare case customer actually needs access to all history tables. Keep shadow tables from being loaded in DB platform / platform's DDL Reader. See also: https://dataedo.com/kb/query/sql-server/list-temporal-tables-in-database https://learn.microsoft.com/en-us/sql/relational-databases/tables/temporal-tables?view=sql-server-ver16 |
||