The document discusses challenges with database change management in complex environments where changes need to run smoothly across systems including cloud and on-premises databases. It emphasizes the importance of change management to ensure transitions occur without damage. It then provides examples of a case study where automated database deployment and change management helped a large healthcare company by reducing human errors and interventions during the deployment process.

1. Automation:
Code Deployment and Database Change Management
-Prasad Vemuri
Trans AppData Technologies , Hyderabad, India.

2. Expectations and Challenges: Database Change
management
➢ In increasingly complex Environments, any small change needs to be able to run smoothly across
the system, which likely includes DB on Cloud and On Premises.
➢ For these reasons, it is extremely important to stay on top of database change management to
ensure that transitions and revisions occur without causing damage.
➢ Most significant business applications rely on at least one relational database for persisting data.
➢ As new features are developed, database schema changes are often necessary – i.e. new tables,
columns, views, and stored procedures.
➢ Database schema changes and corresponding code changes must always be deployed together.
➢ Using continuous integration for database changes.
➢ Build, testing and deployment of DB changes carried out through a proper database release
process.
➢ The goal of change management is to make the result of any change predictable, minimize the
risks associated with that change, and mitigate the impact of failure of the change.
➢ Database change management pertains to changes in the architecture, structure, or logic of
databases.

3. Business Drivers
➢ Source code and Version Control.
➢ Automation in Code Deployment.
➢ Consistency & Reducing/ Avoiding Human Errors in deployment.
➢ Robust and Cost effective solution.
➢ Proper Ticketing system for change tracking.
➢ Smooth and United efforts from Development and Operations.

4. Case Study
Change Tracking for a large Health care company having Involvement of the
Database Administrators doing the code deployment, having a Robust Source /
Version Control system.
Pain Points
➢ Performing Manual Steps in code deployments leading to Improper Executions
➢ Increased Human intervention while deploying the code.
➢ Maintenance of a Separate Version Control for closing the coordination gaps by
Execution team and Development teams.
➢ Not having a Uniform Change Tracking system for different SQL compliant
Relational Databases.
➢ Deployment plans being RDBMS Vendor dependent procedures.

5. How TAD can Help
➢ Configure and make the Deployment Vendor Independent
➢ Automate the Process of Deployment Uniform for any RDBMS
➢ Integrate the Deployment thru Jenkins and Ansible with full control.
➢ Fine control with facility to skip already applied changes and apply the Change
request as expected.
➢ Error and Message tracking of failed Builds.
➢ Reduce Human intervention and Manual Changes.

6. Build Log Sample
'MASTER'
'DB Build 1.0.0.1 102464 Already run '
'DB Build 1.0.0.1 102464 Already run '
'DB Build 1.0.0.1 102465 Already run '
'DB Build 1.0.0.1 102465 Already run '
'DB Build 1.0.0.1 102466 Already run '
'DB Build 1.0.0.1 102466 Already run '
'DB Build 1.0.0.1 102467 Already run '
'DB Build 1.0.0.1 102467 Already run '
'DB Build 1.0.0.2 102468 Already run '
'DB Build 1.0.0.2 102468 Already run '
'running 1.0.0.3'
@/tmp/Build1/1.0.0.3/1.0.0.3_insertdept.sql
'running 1.0.0.3'
@/tmp/Build1/1.0.0.3/1.0.0.3_insertemp.sql