blog: add a post on running two rule sets against one table

Capture all four screenshots against a licensed instance, and add the concurrency caveat: mp_lockanytable and the MPE_DATALOADS staleness check both key on (libref, dsn), so two registrations of one physical file do not serialise against each other.
2026-09-24 17:08:04 +00:00
1 changed files with 1 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* 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](#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