Implementing change management (DI Studio functionality) in an existing environment

[Anne_A]

Hi everyone,

Does anybody have some experience in implementing the change management facility in DI Studio AFTER a DataWarehouse has been created? The DI explanations I've found so far explain how to use, and I assume people who install / configure the application know how to set up the change management facility, but I'm wondering how / whether it could be "added" to an existing DataWarehouse.

Many thanks in advance!

Anne.

[LinusH · Accepted solution]

Do you refer to the check-out/check-in functionality?

I know SAS refers to change management in this context which I think is a bit misleading.

Regardless, hopefully you have a dev environment separated from prod.

This is only applicable to dev,

And I don't see that it should be any hassle set this up this at any time, it may be a bit time consuming to outline all current user authorizations that you have  today, and change it accordingly to "change management".

[Anne_A]

Hi @LinusH ,

Yes I refer to the check-in / check-out functionality (an I agree SAS wording for it is misleading). Thanks for the reply.

[Anne_A]

Thanks (again) @LinusH . As a follow-up to that question, how would you suggest the workload to implement such a change (again, to an existing, real life real customer DataWarehouse) should be estimated? I am just asking about the technical changes, excluding the learning curve (easy) and change of process / culture (less easy) of the people involved.

Many TIA.

[LinusH]

Quite hard to tell, depends on several things, like

- general SAS intelligence platform competence

- no of developers

- any required deviations from a "standard" pattern (this could be that some users should have check-in/check-out on certain objects/folders, but RW on certain objects)

- complexity of the existing DW (no folders, libraries, object types).

I suggest you first do an assessment and "design", and then make the detailed plan.

[ErikLund_Jensen]

Hi @Anne_A 

The SAS documentation has a good description of the steps in setting up change management. It is not complicated. see

https://documentation.sas.com/doc/en/bicdc/9.4/bidaag/p0jwlqhvab11lrn130hwdiq02tsi.htm

In addition, you might want to do something with autorizations on the Custom Tree folder to prevent users from making direct changes without use of check-out and check-in.