Last modified by Phillip Swanepoel on 2024/10/10 12:42

<
From version < 2.1 >
edited by Phillip Swanepoel
on 2024/10/10 09:09
To version < 1.10 >
edited by Phillip Swanepoel
on 2024/10/10 06:38
>
Change comment: (Autosaved)

Summary

Details

Page properties
Content
... ... @@ -1,4 +2,3 @@
1 -(All scripts used are stored on the managed instance under "D:\SKL_Staging_Everest\~_~_skl\scripts" - To be moved to source control)
2 2  Create Files and Folders using current standards (Currently copied from working copy).
3 3   - Rename folder in inetpub/wwwroot to new domain
4 4  
... ... @@ -18,24 +18,4 @@
18 18  Create database using current naming scheme in azure (currently by copying a current working database, with the data removed in a later step).
19 19   - User Groups are added automatically through a job within 5 minutes.
20 20  
21 -Setup SVC users and delete base database users using "SKL_sqlmi_accesss_SKL.sql" 
22 - - Enable SQLCMD mode under Query > SQLCMD Mode
23 - - Client Code: Three Letter Acronym
24 - - TargetEnv: Live | Staging
25 - - ClearLogins: 2
26 - - Passwords in script to be updated to the ones used above
27 -
28 -Update Synonyms for Documents and Audit if relevant
29 -
30 -Remove old data using the script "\Dropbox\EBSphere\Everest SQL\Special Scripts\_Debug Scripts [DO NOT RUN]\Script for new Database [DO NOT RUN]\Clear Data [DO NOT RUN].sql"
31 - - Ensure that you DO NOT run this on the wrong database
32 -
33 -Truncate the documents db
34 -
35 -Run dba.dbo.sp_scan_db '%CLIENT[_]%','CLIENT_ENV_Everest' to identify any scripts or tables with old references and update them to reference the new database and client
36 -
37 -Create STP using Everest Administrator
38 -
39 -Create license using new STP
40 -
41 -Test new STP
20 +

Need help?

If you need help with XWiki you can contact: