What is the process for updating a database schema for a Cobalt module?
in TR Internal
What is the process to update an Oracle schema as part the changes in an iteration for a Cobalt module?
Tagged:
1
Best Answer
-
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.aspx2
Answers
-
This answer makes reference to the "Rest of the process" and the "Normal schema change process". It would be great if that process was also identified0
-
It is identified in the (). I will update the original post to make that obvious.0
-
Here is a document a proposed formalized procedure for schema changes:
http://tfsnpt.int.thomson.com/Shared%20Documents/DevelopmentOperations/Cobalt%20Database%20Change%20Management%20Process.docx0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛