Rename and switch ownership of legacy 2017 databases

[MikeTheCanuck]

Getting all the 2017 databases under one roof, I'm thinking about me or another person in the future wrangling all the databases as more come online, and thinking that names and users that don't follow a common pattern are going to be hell when it comes time to automate operations (e.g. moving database backups around, migrating, etc) - and becomes just unnecessarily hard to remember what database went with which API project.

I mean to bring the 2017 databases up to the same naming conventions as we have for the 2018 databases. That means renaming databases and swapping owners - historically not something that most of our developers have found easy, and I don't know the proper procedures off the top of my head either. So here goes writing down the plan and how it gets executed.

Inventory of legacy databases

• Budget project:
  • db owner: budget_user
  • databases: budget
• Emergency Response project:
  • db owner: eradmin
  • databases: disaster, fire, police, test-disaster
• Homelessness project
  • db owner: homelessness_user
  • databases: homelessness
• Housing project:
  • db owner: housing
  • databases: housing_user
• Transportation project:
  • db owner: transportation_user
  • databases: transportation

The major change I'd like to make is for the Emergency Response project:

• db owner: emergency-response
• databases: emergency-response-disaster, emergency-response-fire, emergency-response-police

And it would be helpful to rename all the {budget_user, homelessness_user, housing_user, transportation_user} to {budget, homelessness, housing, transportation} or even {budget-readonly, homelessness-readonly, housing-readonly, transportation-readonly}. Then every database operation can do something like for database in databases and just equate "project name" to "database owner". Makes it as easy as possible to equate "user" with "databases associated with that user" too.

[znmeb]

Are those the current names?

[MikeTheCanuck]

That’s exactly how they’re found in the wild

[znmeb]

I'm not sure why you'd want to rename and re-own a database unless the database names match one of this years'. Role creation is easy and doesn't occupy a lot of disk space. I think it's just a couple of small rows in small tables.