At my company we are re-assessing which developers will take on the deployment for
xyz ticket. At the moment when a developer is done with his ticket, a deployment ticket is created and another developer will take it, do the code review and test the change(s).
We have 3 databases
The problem is that we don't really have a real DBA, only someone assigned to validate and run the databases changes. In the development environment we(developers) own the DB and have all the rights, but when we make a ticket for the deployment(which requires the staging DB for testing) we don't have the necessary rights and this is where, i think, there is a problem since we need to create a new ticket to have our SQL changes run on the staging DB and it may take some time before those changes are made. After all the review, test and feedback processes we're ready to push the new changes into production, however we're blocked again and need to make another ticket to have our SQL run in the production environment.
My 2 cents on this is that since developers do the deployment and the staging database is for the deployment we should be the owners and making ticket after ticket is just a waste of time because it slows down the deployment process and has side effects for our clients because new features/bug fixes don't come as fast as they should because we're stuck with ticket after ticket.
Who should own the staging database and why?