Start with the databases that are very critical to core business functionalities to ensure that the most vital services are prioritised for stability and performance.Then, focus on identifying and addressing the most impacted databases.

1.Assess Severity and Impact: Evaluate the issue's impact on business operations and classify it as Critical, High, Medium, or Low. 2.Use an Urgency Matrix: Plot issues on a matrix with Severity (High, Medium, Low) and Urgency (High, Medium, Low) axes to determine priority. 3.Prioritize Critical Issues First: Address Critical and High-priority issues immediately, followed by Medium and Low-priority issues.

Primeiramente verificaria se alguma aplica??o de baixo impacto para o negócio poderia ser desligada, para diminuir a carga dos bancos de dados. Logo na sequência focaria nos bancos de dados que tem mais impacto para o negócio, solicitaria ajuda para colegas de confian?a, cada grupo de colegas olharia as queries que est?o consumindo mais recursos do banco e tentaria otimiza-las criando índices ou modificando as consultas. Reuniria uma outra equipe em paralelo para monitorar a aplica??o e verificar se conseguimos modificar algo no código colocando filas de processamento para diminuir a carga do banco de dados.

Here are some of the immediate actions we could do - Check monitoring tools like SQLSentry to understand what is causing the issue - Bad plans can be mitigated by recompiling procedures, the dev team can investigate and fix the code. - Deadlocks and locking could be released to allow critical apps to function - Fix the database that has more business impact and hard SLAs. - Having lower environments close to production can help eliminate performance issues leaked to production. - Have observability tools like Datadog to monitor, alert anomalies before it gets widespread.