5.4.1Database Upgrade Impact

This matrix shows the impact of upgrading each release on the various Smile CDR databases.

Note the following table only provides a rough relative guideline of the impact of performing an upgrade on the Smile CDR databases. The actual impact on your particular databases may vary greatly and we recommend that you keep track of your own database upgrade performance as you move through the various Smile CDR releases.

Release	Cluster Manager	Persistence	Audit Log	Transaction Log	Overall	Comments
2023.08						25 indexes are added to the Persistence Database, however most of them are on small tables. The overall migration time should not exceed a few hours.
2023.11	LOW	HIGH	NONE	NONE	HIGH	The Persistence database undergoes a huge migration to fix the padding on the FORCED_ID column for all resources in the HFJ_RESOURCE table. This migration is performed in chunks of 100,000 resources. The FORCED_ID script is executed twice during schema migration. This will take a significant amount of time for databases that contain a large number of resources.
2024.02	LOW	MEDIUM	NONE	LOW	LOW	This release adds a couple of indexes to the HFJ_SPIDX_* tables. For customers that have a large number of rows in HFJ_SPIDX_STRING and HFJ_SPIDX__URI tables, this could take quite a while to complete (e.g. several hours).
2024.05	HIGH	HIGH	HIGH	HIGH	HIGH	This release involves migrating the large objects to inline storage for PostgreSQL databases. Depending on the number of large objects present in the database, this could take anywhere from a few hours to a few days to complete.
2024.08	LOW	MEDIUM	NONE	NONE	LOW	This release adds a couple of indexes to the HFJ_SPIDX_URI table. For customers that have a large number of rows in this table, this could take a while to complete (e.g. several hours).
2024.11	LOW	NONE	LOW	NONE	LOW	This release adds 2 new indexes to the CDR_AUDIT_EVT_TARGET_RES table.
2025.02	LOW	LOW	LOW	LOW	LOW	This release adds a RESULT column to the FLY_HFJ_MIGRATION table and a PARTITION_ID column to several tables in the FHIR database to support database partitioning mode. This release also drops foreign keys from the HFJ_HISTORY_TAG, HFJ_RES_LINK, HFJ_RES_SEARCH_URL, HFJ_RES_TAG, HFJ_RES_VER_PROV and HFJ_SUBSCRIPTION_STATS tables.

5.3 Upgrade Best Practices 5.5 Appendix and FAQ