From ad5a566001cb59fe82b25647a653ba1a9eb5207d Mon Sep 17 00:00:00 2001 From: allan Date: Mon, 30 Mar 2026 23:01:24 +0000 Subject: [PATCH] fix: doc improvements --- docs/admin-services.md | 1 + docs/dci-deploysas9.md | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/admin-services.md b/docs/admin-services.md index 46936a4..8c2fe6e 100644 --- a/docs/admin-services.md +++ b/docs/admin-services.md @@ -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| diff --git a/docs/dci-deploysas9.md b/docs/dci-deploysas9.md index a2624de..765b9ad 100644 --- a/docs/dci-deploysas9.md +++ b/docs/dci-deploysas9.md @@ -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