fix: mentioning DI in redeployment on sas 9

docs/dci-deploysas9.md

@@ -40,7 +40,7 @@ Deploy as follows:
 3. Open the `index.html` file and update the values in the `<sasjs>` tag as follows:
 
   * `appLoc` - same as per SAS code in the section above
-  * `serverType` - change this to`SAS9` 
+  * `serverType` - change this to`SAS9`
   * `serverUrl` - Provide only if your SAS Mid Tier is on a different domain than the web server (protocol://SASMIDTIERSERVER:port)
   * `loginMechanism` - set to `Redirected` if using SSO or 2FA
   * `debug` - set to `true` to debug issues on startup (otherwise it's faster to leave it off and turn on in the application itself when needed)
@@ -169,14 +169,15 @@ The full redeployment process is as follows:
     - To a new metadata folder
     - To a new frontend folder (if full deploy)
 * _Delete_ the **new** DC library (metadata + physical tables)
-* _Move_ the **old** DC library (metadata only) to the new DC metadata folder
+* _Move_ the **old** DC library (metadata only) to the new DC metadata folder.  You will need to use DI Studio to do this (you can't move folders using SAS Management Console)
 * Copy the _content_ of the old `services/public/Data_Controller_Settings` STP to the new one
     - This will link the new DC instance to the old DC library / logs directory
     - It will also re-apply any site-specific DC mods
 * Run any/all DB migrations between the old and new DC version
-    - See [migrations](https://git.datacontroller.io/dc/dc/src/branch/main/sas/sasjs/db/migrations) folder 
+    - See [migrations](https://git.datacontroller.io/dc/dc/src/branch/main/sas/sasjs/db/migrations) folder
+    - Update the metadata of the SAS Library, using DI Studio, to capture the model changes
 * Test and make sure the new instance works as expected
-* Delete (or rename) the **old** instance 
+* Delete (or rename) the **old** instance
     - Metadata + frontend, NOT the underlying DC library data
 * Rename the new instance so it is the same as the old
     - Both frontend and metadata