/sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/ Recent content in Database Updating on Hugo -- gohugo.io /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/introduction/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/introduction/ This document describes the steps that must be followed to update a SICS schema of a previous version to version 26.1. The procedure requires a SICS System Administration Utility where the user is logged in as the owner of the database schema to be updated. It is highly recommended that you take a backup of the database before you run the update. If the update should fail it may be necessary to revert to this backup. /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/procedure/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/procedure/ Enable database optimizations (optional) # When upgrading it is possible to automatically apply database optimizations to a database through a patch. This can be achieved by turning on optimized mode before applying database patches. Please refer to the comments in conf/sics-database-sources.xml for a description on how to enable the optimized mode for a specific datasource. Optimizing an existing database through database patch requires time and space and should be considered as an option only when dealing with small databases. /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/updating_access_security/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/updating_access_security/ If there are changes in use cases, these will need manual updating of the security settings. Updates of Use Cases # Changes in Security use cases should be updated on the SICS database using the “Update Security” function on the System Administrator console. The “Update Security” process will: Delete use cases that have been removed. Add new use cases to the database. Update changed use cases. Note: The modified and added use cases have notes added to each access right. /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/refresh_database_views_after_database_upgrade/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/refresh_database_views_after_database_upgrade/ The below mentioned steps are applicable for SQL server database : FIRST PART RUN THE BELOW SQL THIS WILL GENERATE A NEW SCRIPT WHICH WILL UPDATE THE REPORTING VIEWS WITH NEW DATABASE TABLE DEFINITIONS SELECT 'exec sp_refreshview ' + TABLE_NAME + ';' FROM INFORMATION_SCHEMA.VIEWS WHERE TABLE_SCHEMA = 'SICS_PC' ; SECOND PART, COPY THE RESULT FROM THE FIRST SELECT PART AND RUN IT - THIS WILL REFRESH THE DATABASE VIEW DEFINITOINS. BELOW IS A SHORT EXAMPLE OF THE RESULT FROM THE 1ST QUERY exec sp_refreshview V_SJ_BC_ADJUST_DER; exec sp_refreshview V_SJ_BC_INSTAL0_DER; exec sp_refreshview V_SJ_REF_CHILD; /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/additional_information/ Mon, 01 Jan 0001 00:00:00 +0000 /sicsdocs/sys_admin_guide/sys_admin_utility/database_updating/additional_information/ Using Schema Browser as a QA tool # Optional - After the database upgrade is completed use the Database Schema Browser to verify the structure on the upgraded database. Please remember to take a backup before removing database objects and use SICS Database Schema Browser to verify database after changes. The usage of SICS Database Schema Browser is described in DXC SICS Database Schema Browser.