3.4 KiB
3.4 KiB
title, description, date, author, authorLink, tags, previewImg
| title | description | date | author | authorLink | tags | previewImg | |
|---|---|---|---|---|---|---|---|
| SAS-isms: Library Info | Expanding a VIEW library in Data Controller surfaces engine, size, paths, table count and schema - with the same data queryable from the underlying tables. | 2026-08-11 09:00:00 | Data Controller | https://www.linkedin.com/showcase/data_controller |
|
./library-info.jpeg |
Library Info
One of many "SAS-isms" in Data Controller for SAS®.
When expanding a VIEW library, Data Catalog items are surfaced:
- Library Engine
- Library Size (Bytes, MB, GB)
- Paths (if BASE engine)
- Table Count
- Schema (if a database)
And more. Much of this data can also be queried from the underlying tables:
- MPE_DATACATALOG_LIBS - engine, paths, permissions, owners, schemas, metadata name / id
- MPE_DATASTATUS_LIBS - frequently changing attributes: library size, table count, catalog count
The split is deliberate - stable attributes live in the DATACATALOG tables, volatile ones (size, counts) in DATASTATUS. All of it is stored with SCD2, so you can track how your data landscape changes over time.
Refreshes are driven by the mpe_refreshlibs and mpe_refreshtables macros - any user can refresh an individual library from the VIEW menu, and admins can scan the entire estate from the System page.
Similar information is available for datasets - it's essentially an extract from proc contents, using the mp_dsmeta macro from the SASjs Core library.
