dc/docs.datacontroller.io
5
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: doc improvements
All checks were successful
Publish to docs.datacontroller.io / Deploy docs (push) Successful in 1m3s
Details

Browse Source
This commit is contained in:
allan
2026-03-30 23:01:24 +00:00
parent 15c617f48e
commit ad5a566001
2 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/admin-services.md
View File

@@ -16,6 +16,7 @@ Button info as follows:
|Button|Description|
|---|---|
|Refresh Data Lineage|This is only displayed for SAS9 installs. Will refresh all TABLE level data lineage (impact analysis) using an efficient batch approach (proc metadata).|
|Refresh Data Catalog|Update Data Catalog for ALL libraries. More info [here](/dcu-datacatalog).|
|Download Configuration|This downloads a zip file containing the current database configuration - useful for migrating to a different data controller database instance.|
|Update Licence Key| Link to the screen for providing a new Data Controller licence key|

2
docs/dci-deploysas9.md
View File

@@ -169,7 +169,7 @@ 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. You will need to use DI Studio to do this (you can't move folders using SAS Management Console)
* _Move_ the **old** DC library (metadata only) to the new DC metadata folder. You will need to use DI Studio to do this (as you can't _move_ objects 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