Recommendations for designing a Change Management strategy

An effective change management strategy is one that is well planned. The most important factor to consider is to ensure that changes to a set of objects are either all performed through Change Management (CM) or are all performed without Change Management.

Requiring that all changes go through Change Management is easy when the objects that should go through Change Management are handled by a few SQL IDs and the SQL IDs are used only for these objects. If the SQL IDs are also being used to change objects that should not go through Change Management, you should set the Change Management level option to OPTIONAL, and the user will have to decide whether the change should go though Change Management.

A few example Change Management strategies are:
  • When Change Management is being used for the objects for only one application:
    • Set the Change Management level for the SQL ID that is used to manage the objects for the application to REQUIRED.
    • Set the level for the other SQL IDs to NONE by setting the default Change Management level to NONE.
  • When Change Management is being used for the objects for all applications except for a few objects that are under design and development:
    • Set the default Change Management level to REQUIRED.
    • Set the Change Management level for the SQL IDs that are used to change the objects that are under design and development to NONE. If those SQL IDs are also used to change objects that are not under design and development, set the Change Management level for the SQL IDs to OPTIONAL; the user will need to specify whether to use Change Management upon each change.
  • When Change Management is being tested:
    • Set the default Change Management level to OPTIONAL.