I've found that occasionally when promoting changes of Repository Table definitions from the Development to other environments (e.g. Test and Production) DI Studio makes mistakes and keep some of the old columns that been removed or renamed. If these mistakes are detected and corrected then promoted jobs can generate incorrect code that always produces errors or warnings. Using Proc Contents (or querying Dictionary tables) I can see what the actual columns in a table are, and manually correct the mistakes.
What I would like though is a way to (semi-) automatically compare the metadata table definitions with the actual structures found in the database.
Has anybody done this kind of comparison?
Hi Dave - this macro may help (credit to @PaulHomes who wrote the original):
https://core.sasjs.io/mm__getlibmetadiffs_8sas.html
If you are interested in finding more issues with your SAS 9 metadata, we built a "plug and play" scanner that can find all kinds of health issues in a SAS 9 environment, as such as dangling metadata, security misconfigurations, SAS coding issues, custom code in DI Studio, missing primary keys, etc. Well over 100 different checks. Do get in touch if you'd like to give it a whirl.
SAS Innovate 2025 is scheduled for May 6-9 in Orlando, FL. Sign up to be first to learn about the agenda and registration!
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.
Find more tutorials on the SAS Users YouTube channel.