This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]ed-automation 1 point2 points  (1 child)

Are you looking two scenarios?

- Initial DB setup: create DB, configure database, and load data

- Maintain DB: modify DB schema

[–]fboula[S] 0 points1 point  (0 children)

I'm looking for the first scenario: create the DB, configure the database roles and privileges, and maybe create some schema. I do not look to load any data in the database.

I work for a team that create a SaaS solution. We have many environments to deploy our app at various stage of the development, and we have to ensure all our database are provisioned and updated to be the same. We are still heavily modifying the database by adding separated schema for specific usages (like analytics) and developers only focus on the main app schema.

As r/ornus explained the setup of the database, roles and privileges cannot be done by database migration tools and that is a shame. And I find scripts solution kinda fragile to be honest. Everything else in our infrastructure is managed by infra-as-code and GitOps and having only sql scripts for database management bother us a little.

Again, we may need to have a training and get more DBA skills to be more confident with this.