Change Request Form

DH CIMS & IHDatabase DeploymentChange Request Form v1.0DH CIMS& IHDatabase DeploymentChange Request Form

Notes: (Version 1.0)Prerequisite: The review process for the revised/new design should be done before DB deployment request. Project teams should perform quality checking on the DB schema/data script before passing to Data Team for DB deployment. The DB deployment change request form or DB deployment special change request form should be submitted by eHRMT project team member.

Normal Flow: Excluding the review process, DB deployment request should be made 3 days for DEV/UAT/TRN DB and 5 days for production DB in advance by submitting the DB deployment change request form. DB Deployment request will be arranged in first-come-first-serve basis. DB Deployment request should NOT be scheduled on office hours except DEV DB. For the DB deployment to the Production Environment, side-by-side DB deployment from the Contractor may be required upon request.

Special Request: For non office hour DBA support, it should be reserved and submitted3 days ahead. Due to limited resource in Data Team, it is not guarantee your request can be arranged. For interim solution or special DB privilege/configuration request, DB deployment special change request form should be submitted 5 days in advance. This form should be approved by the eHRMT Project Teams manager and Data Team might consider such request on a case-by-case basis.

The following parts are to be filled in by the Requester

Subject:To apply table constraint and comment for 4 IVG table fields in UAT, TRN, PRD

Project Team:CGS

Requested By:Simon Leung (CGS team)

Requested Date:22-7-2014

Scope:CIMS

Environment:UAT, TRN, PRD

Expected Deployment Date: ([footnoteRef:1]at least 3 days lead time is required) [1: Assuming the schema design was already reviewed by the Data Team during the SA&D phase and no change has been applied thereafter.]

25-7-2014

Impact:Common Schema

Perform Quality Check:Yes / No

Patch ID:

Patch File Name (specify the patch sequence if more than one file):ivg_table_type_def-mh.sql

Patch File Verified by:Miranda

Patch File Verified on:22-7-2014

Any special DB privilege is needed:(*You may need to submit a separate SPECIAL change request form)no

Any special label security is needed:(*You may need to submit a separate SPECIAL change request form)no

Non-office hour deployment is needed:Yes / No

Fall Back Plan:Revert to latest patch ID

Remarks:

The following parts are to be filled in by DATA Management Team

Investigated by:

Ref No.:

Handled By:

Remark:

Disclaimer:

Interim work-around:- As an interim work-around deployment, data team will proceed deploying your script to the CIMS DEV environment. Once we deployed the interim work-around, it is assumed that your team had understood the comment and commit to fix the issue within your project. In case it does not align with your understanding, please raise and discuss to resolve the gap. Thanks.

Stored procedure (SP):- Regarding the SP, Data Team will simply deploy the SP as is. It is presumed that project team shall make sure the stored procedure is enabled with logging and debugging capability. In case there is run time error induced by the stored procedure, project team shall have a mechanism to troubleshoot the issue and debug.

1