topic Re: Renaming SAS Folder containing tons of LASR and Source Table Information in Administration and Deployment

Renaming SAS Folder containing tons of LASR and Source Table Information

Djones4822 — Wed, 05 Dec 2018 15:29:07 GMT

We are running SAS 9.4M5 and SAS Visual Analytics 7.4

We structured our SAS Folder Directory similar to this

| SAS Folders 

---| Departments

--------| Sales

-------------| LASR Tables

-------------| Source Tables

-------------| Reports

-------------| Queries

--------| Marketing

-------------| LASR Tables

-------------| Source Tables

-------------| Reports

-------------| Queries

---| (Other SAS FOLDERS)

This has become inadequate and I've been asked to restructure so that "Departments" is used purely for reports and a new folder called "Data Sources" holds the LASR/Source/Queries information.

Is this possible? My plan was just to rename the existing folder to "Data Sources" and create a new "Departments", but if I rename the folder from "Departments" to "Data Sources" then all the metadata associated with the source tables would need to be updated, correct?

Is there an efficient or more effective way to rename the folder so that all the Source metadata and LASR information isn't screwed up?

Thanks!

Re: Renaming SAS Folder containing tons of LASR and Source Table Information

JuanS_OCS — Wed, 05 Dec 2018 15:39:58 GMT

Hello @Djones4822,

this is a really great question. Thanks for raising it.

I wonder what other think about it. My general best suggestion is to use metadata promotion (export / import spks), without the dependencies and in the right order od dependencies.

In that way, wehn you import, the import wizard will prompt you to provide the new mappings for its dependencies of the object.

However, once this is done, you probably should reload the data, and you might need to adjust any code/based operation, such as data queries and such, enything that would be using SAS metadata paths. Hence, you might want to do a good inventory upfront and action plan.

Your metadata security might suffer too, in the sense that the security will change after the folder structure change, right?

In any case, if you have a development/test environment, better to start there, to ensure there is no impact in your production environment, but also to ensure every step is clear and recorder when you apply it in production, to reduce time and even possible downtime to minimum.