What is the process for updating a database schema for a Cobalt module?

Ryan Morlok

What is the process to update an Oracle schema as part the changes in an iteration for a Cobalt module?

Lavanya Gundamaraju

Starting 14.2, Database Schema change review process will be implemented as follows

1. Developers will create Schema change scripts
2. Developers will create TFS Database CR request, identify application version, assets and upload the scripts to the tfs request before **1:30 PM Monday** (the Monday after the iteration start)
3. Developer attends schema change review meeting at 10:30 AM CST on Tuesday to explain the changes
4. DBA’s will provide feedback about the scripts to the developers on Tuesday and will approve
5. Based on the feedback, development team will update the scripts and resubmit for approval
6. DB Change Coordination will cut service center CR for DBAs based on the TFS Database CRs submitted by the development team
10. If the development team needs scripts to be reviewed outside of the above schedule, they should work with the DB Change Coordination team directly and ensure that the review is completed before the Friday meeting
11. Normal schema change process will continue to be followed after this point. That is, The Thusday meeting to go over the script changes if any & CR execution by DBA's 2 days prior to code deploy.

**Note:**

a. TFS Schema Change CRs need to be submitted after the review so CM can kick start the change implementation process

b. It is very important to attend Schema change meetings and make sure the DBAs fully understand the change and its scope

c. CM will continue to attach scripts to the Service manager CRs for DBA



[1]: https://theshare.thomsonreuters.com/sites/DBA/CPSDBA/cobalt/default.aspx