Changes for page MI Restore to Staging From Live
Last modified by Phillip Swanepoel on 2026/06/09 12:46
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -22,15 +22,12 @@ 22 22 11. recreate tblDocuments synonym 23 23 11. tblAudit if applicable 24 24 25 -1. Run dba.dbo.sp_scan_db script for '%[_]Live[_]%' (exec dba.[dbo].[sp_scan_db] @includestr = '%DBC[_]Live%', @databasename = 'DBC_Live_Everest')25 +1. Run dba.dbo.sp_scan_db script for '%[_]Live[_]%' 26 26 11. correct all config found and repoint to Staging 27 27 11. TODO automate (some of the config correcting statements can be generated using [dba].[devops].[sp_change_db_env_post_restore]) 28 28 11. exec dba.[devops].[sp_change_db_env_post_restore] @dbname = 'ENV_Staging_Everest', @ClientCode ='ENV', @Sourceenv = 'Live', @TargetEnv = 'Staging', 29 29 @domainRev = 'com.site', @domain = 'site.com',@svcUserPass = 'xxx.xxx.xxx.xxx#xx' 30 -11. After executing the output of the dba.devops.sp_change_db_env_post_restore rerun this SP and make sure there is no objects that hasn't changed 31 -11. Use [[doc_central.sql - Repos>>url:https://dev.azure.com/ebsphere/ebsphere/_git/devops?version=GBmaster&path=%2Fsetup-scripts%2Fdoc_central.sql]] to update staging documents when restoring from live. 32 32 1. Start all services 33 33 11. check logs to make sure no connections issues 34 -1. Log into the new DB with Everest and do a happyline test -> search for a member -> view member details -> upload a document -> download a document 35 35 36 36