Stored Processes - change management?

[AndrewHowell]

Question has been asked: On a SAS 9.4 platform, can Stored Processes be change managed (CheckOut to a project repository, etc)?

The default is no, how easy/hard/impossible is it to change it to a Change Managed object?

:

[Mark_sas · Accepted solution]

The only change management approach for stored processes of which I'm aware is to point the associated stored process code to a server location which itself reflects a publish from an external source management utility.

[AndrewHowell]

Mark,

Had a similar thought where the stored process metadata object itself may not be able to be change managed, but the underlying code is save as a *.sas file which me manage via a DI User Code node (similar to how we manage macros).

This is the first time I've encountered a site which wants to change manage "everything", and since we're using DI projects to change manage the bulk of the ETL work, they've asked if it can be extended further. Didn't realise til now that you COULDN'T change manage stored processes - seems an odd gap.

Regards,

Andrew.

[Kurt_Bremser]

In light of your question, I would like to see it that _all_ metadata objects could possibly be subject to change management/historization (on a technical level). Building on that, SAS could then turn that on by metadata object type.

Think of being able to see who did a change to a user definition at a given point in time. Or why the authorization on a library was changed.

[AndrewHowell]

@Kurt_Bremser - concur totally; ideally let the admin control which metadata types are or are not change-managed.