You’re offline. This is a read only version of the page.
Symptom:
When upgrading from BC 14 to BC 17 you might notice that differences in the handling of VSIFT indexes on the SQL side are different from all other SQL objects of the database when an upgrade is performed.
Every table and its indexes were renamed, but views and their index were dropped and recreated.
During this operation, a former compressed index of the view will be recreated without compression. The renamed tables and their indexes are still compressed.
Analysis and clarifications:
As all of us know that We never guarantee any customizations done directly in SQL survive schema syncing
Latest 14 does support compression, both from C/SIDE and extensions:
From 16.x and forward, you can also simply run Start-NAVDatabaseCompression after the upgrade stating the level you want. This will query SQL for tables/indexes with incorrect compression and compress them, and set the 'default' level going forward for new tables synced (that don't have the compression level explicitly stated).
Reference:
2. Start-NAVDatabaseCompression
Share
Report
All responses (
Answers (
2,785
