Database may crash due to data collation conflicts with different DB between app and DB teams
Risk Description:
DB team states DB may crash due to collation issues with incoming data now using SQL 2019 and current data is SQL2012
Mitigation Plan:
Will begin testing next week with a new replicated transaction. Otherwise, we will need to upgrade the DB
Analysis
Probability: 5
Severity: 5
Risk Score: 25
Timeline
Open Date: 04-10-2024
Trigger Date: 08-10-2024
Closed Date: 08-22-2024
Aging Days:
12
Classification
Status: Closed
Owner: Chris Freeman
Project ID: PMO-2024-034-001
Risk Logs & Notes
| Date | Owner | Note |
|---|---|---|
| 04-18-2024 | Chris Freeman | DB team conducted testing, and seems to be not a system collation issue, but a data entry issue. In 2023 the AR team began revising their date formats based on new management direction. Issue could be resolved by a revisions script. |
| 03-14-2024 | Chris Freeman | Meeting with DB team was inconclusive, as some members feel the 2019 collation should continue working with the 2012 records. |
| 03-04-2024 | Chris Freeman | The Finance team implemented a different collation when they upgraded in 2023 to SQL2019. But this ws a one off. Met with Richard today, who stated IT was aware of the upgrade. Scheduling review with IT, Bonds and DB team, to understand depth of the issue |