Author SHA1 Message Date
allan ae3f5128c2 Merge pull request 'feed: add a who-is-it-for post for Data Controller' (#22) from feed/who-is-data-controller-for into main
publish / Build-and-publish (push) Successful in 3m57s
Reviewed-on: #22
2026-09-26 20:24:46 +00:00
blog-dev bc44d4cf73 feed: use the generated cover for the who-is-it-for post 2026-09-26 20:10:08 +00:00
blog-dev 838bc7a96f feed: correct the Excel retention wording and mention rollback 2026-09-26 20:10:08 +00:00
blog-dev 53c0de0960 feed: add a placeholder cover for the who-is-it-for post 2026-09-26 19:53:21 +00:00
blog-dev 549ecc36aa feed: add a who-is-it-for post for Data Controller 2026-09-26 19:41:36 +00:00
allan 463de81ffa Merge pull request 'blog: document the concurrency caveat of two librefs over one table' (#21) from blog/concurrency-caveat into main
publish / Build-and-publish (push) Successful in 3m55s
Reviewed-on: #21
2026-09-24 17:22:47 +00:00
dc 79d2e887d3 blog: document the concurrency caveat of two librefs over one table
mp_lockanytable keys its control table on (lock_lib, lock_ds), and the
approve service takes that lock on the base table named in the submit
record. The MPE_DATALOADS staleness check is keyed the same way. So two
registrations of one physical file neither lock nor observe each other,
and a second approval can overwrite the first silently.

Spell that out, note that the hook route routes both mirrors to one base
table and so does not have the gap, and give the two ways to close it.
2026-09-24 17:09:34 +00:00
allan 1119645a00 Merge pull request 'blog: add a post on running two rule sets against one table' (#20) from feed/two-rule-sets-one-table into main
publish / Build-and-publish (push) Successful in 4m19s
Reviewed-on: #20
2026-09-24 16:37:16 +00:00
dc a1513b871e blog: add a post on running two rule sets against one table
Capture all four screenshots against a licensed instance, so the
free-tier licence banner is no longer in frame.
2026-09-24 16:34:29 +00:00
3 changed files with 75 additions and 1 deletions
@@ -48,7 +48,7 @@ There is no copy to keep in sync, no hook to write and nothing to maintain. That
### Things worth knowing
- Where the librefs are defined depends on your platform. On Viya, in the compute context's `autoexec.sas` (or `[DC Drive Path]/services/settings.sas`); on SAS 9, as metadata libraries or in the Data Controller Settings stored process; on SASjs Server, in `services/public/settings.sas`. The one requirement is that each library has a unique libref.
- `mp_lockanytable` keys on `libref.dataset`, so the two menus do not serialise against each other. That has consequences beyond a collision - see [the concurrency caveat](#the-concurrency-caveat) below.
- `mp_lockanytable` keys on `libref.dataset`, so the two menus do not serialise against each other. That has consequences beyond a collision - see *The concurrency caveat* below.
- The audit trail and approval queue record which libref a change came through, so `ORDERS_EU.ORDERS` and `ORDERS_US.ORDERS` stay distinguishable in history. For most people that is a feature - you can see which report a change originated from.
### The concurrency caveat
@@ -0,0 +1,74 @@
---
title: 'Data Controller for SAS® - Who Is It For?'
description: Five roles, five questions - what Data Controller for SAS® answers for administrators, auditors, managers, data owners and purchasers.
date: '2026-09-26 09:00:00'
author: 'Data Controller'
authorLink: https://www.linkedin.com/showcase/data-controller-for-sas
tags:
- Announcements
previewImg: './who-is-data-controller-for.jpeg'
---
# Data Controller for SAS® - Who Is It For?
Data Controller for SAS® gives business users a safe way to add, modify and delete data in SAS tables and databases, without handing them write access to production. That one capability answers a different question for each role that touches the data - so here is the short version, role by role.
## Data Administrators
Would you grant self-serve data updates in SAS if there was no risk to the data model? That is the trade Data Controller offers. End users never get direct write access to the target tables - every change is staged, validated at the point of entry, and applied by the service itself. Data Controller changes data, not structure, so your data model stays as it is.
## Data Auditors
Do you need to know who made a particular data change, what that change was, when it was made, and who signed it off? Every submission carries a full audit trail, and any associated Excel file is retained alongside it, so the source of a change can be reviewed long after it was loaded.
## Data Managers
Do you want to load, modify or delete production data without writing repetitive code, saving sensitive data to shared filesystems, building and deploying jobs, or crafting long-winded change requests? Adding a new editable table is configuration rather than development - the grid is generated from the target table's metadata, and the load type (composite or retained keys, SCD2, bitemporal) is picked from a list.
## Data Owners
Do you like to review data changes before they are applied? Approvers see the diff - new, changed and deleted rows - and nothing lands until it is signed off. Email alerts can tell you when data is changed or about to change, and a completed load can trigger a SAS job downstream. If the wrong change gets approved anyway, the table can be rolled back to a previous state - and the rollback is itself a new, reviewable change, so the audit trail keeps both the mistake and the correction.
## Purchasers
How about a business friendly, no lock-in software licence? The price list is public, every package includes unlimited users, and a perpetual licence is available. The Community package is free, so evaluating Data Controller costs nothing but the installation.
## What it is, in one line
Data Controller for SAS® is a robust solution for secure data uploads into any SAS-connected database, with full audit trail and approval mechanism. Configuration is quick, installation is easy, and everything runs on your own SAS platform with no external calls.
Multiple load types are supported (composite and retained keys, SCD2, bitemporal, format catalogs), data can be validated at the point of entry, and Excel end-user computing files can be dragged straight into SAS. Data Lineage, Data Catalog and Data Viewer come as standard.
Data Control.
Want to see it working on your own data? [Book a Discovery Call](/contact).
<!--
Source LinkedIn post:
Data Administrators - would you grant self-serve data updates in SAS, if there was no risk to the data model?
Data Auditors - do you require oversight of who made a particular data change, what that change was, when it was made, and who signed it off? And to review the original excel, if used as a source?
Data Managers - do you prefer to load / modify / delete production data WITHOUT writing repetitive code, saving sensitive data to shared filesystems, building & deploying jobs, or crafting long-winded change requests?
Data Owners - do you like to review data changes before they are applied? How about receiving email alerts or the ability to set up job triggers after tables are updated?
Purchasers - how about a business friendly, no lock-in software licence?
Data Controller for SAS® is a robust solution for secure data uploads into any SAS-connected database, with full audit trail and approval mechanism.
Installation is easy and configuration is quick. Multiple load types supported (composite / retained keys, SCD2, Bitemporal, Format catalogs). Perform data validation at point of entry. Drag & drop Excel EUCs straight into SAS.
Data Lineage, Data Catalog, Data Viewer.
Data Control.
#sas #sasviya #sasusers #datagovernance
https://lnkd.in/dunqWhnt
Image prompt:
Flat vector illustration, dark slate blue background (#314351), wide 1.91:1 banner (1200 x 627). Five simplified human figures stand in a shallow arc across the centre, each rendered in flat corporate style with minimal facial detail: an administrator beside a padlock, an auditor with a magnifying glass over a document, a manager holding a spreadsheet with an upward arrow, a data owner holding an approval tick, and a purchaser holding a price tag. Behind them, a translucent dashboard panel shows a data grid with one row highlighted as a pending change, and a small diff of new, changed and deleted rows. Thin connecting lines link each figure to the panel, suggesting that every role sees the same controlled workflow. Bright green accent (#90c445) used sparingly on the approval tick, the highlighted row and the connecting lines. Subtle depth with soft shadows, crisp edges. No text, no words, no letters, no logos, no watermarks. Keep the figures and the panel inside the central square so the image is safe to crop to 1:1 - the outer left and right thirds are background only.
-->
Binary file not shown.

After

Width:  |  Height:  |  Size: 138 KiB