Databases

Steps to take when there is the need to access production databases to run queries that retrieve, update or delete data from tables. Other teams sometimes need certain pieces of information from the production DB and would raise a ticket, providing their sql query and requesting PlatOps run these against production Db as they don’t have access to this.

Note: there’s a self service process that should be used by the team if they have an SC person on their team instead.

To fulfill one of these request, you can follow the steps below.

Prerequisites 💥

• Important: Verify you are all setup as outlined in cnp-module-postgres
• Grant yourself access to production Bastion as outlined in cnp-module-postgres, in the Steps to access section of the document
  • Note: If not on call then just one day is sufficient, you could also customize how long you want access for.

Suggested Steps

• Confirm the database connection host. This should be in the ticket, but you can also confirm by searching it in the portal on Azure
• Sanity check the query provided in the ticket, not that you are expected to know any sql 🤥
  • Sometimes typos or misplaced variables are easy to spot
• Jump on to the production bastion, steps on how to do this are in the cnp-module-postgres documentation

Example

Guides

• Connecting to a Database
• Deleting cases from CCD Datastore Database
• Restoring a Database
• Restoring OWASP Dependency Check DB in Sandbox
• Deleting Elastic Search Index
• Create Modes in Postgres Flexible Server

This page was last reviewed on 26 January 2024. It needs to be reviewed again on 26 January 2025 by the page owner platops-build-notices .

This page was set to be reviewed before 26 January 2025 by the page owner platops-build-notices. This might mean the content is out of date.