Ask HN: How do you enforce database standards? How does your team ensure that your database standards are being followed? Naming standards, ensuring certain triggers are present, index/constraint rules, etc. Do you use tools, code reviews, or some other method? I'm finding that this seems to be a harder problem to solve than enforcing other types of coding standards. |
There are other tools like Red Gate https://www.red-gate.com/, and others who sell tooling that works on different databases which allow you to automate a lot of standards and deployments etc. Even works for things like data migrations etc. I've used red gate and tools like it on other solutions, a lot of it depends on the architecture and structure of your project.
For example, tools like Red Gate work great when you have DBA's and developers working together to manage databases (datasets) outside of the application code. It is a more traditional method of data solutions. But as seems to happen in tech, we are back to doing things more from the application and managing structure, migrations and standards through application code. There are valid reasons for both methodologies, so a lot just depends on what you are doing and how your team is structured and how big it is.
Our team consists of a single DBA and around a dozen developers. We're a .NET/C# shop but we use Oracle Databases.
I am not sure with Oracle what is available specifically and it has been a number of years since I worked with redgates tooling, but it was quality stuff. And I remember them being super helpful when we were getting started and answering a ton of questions, so maybe reach out to them with your specifics and see what they have to say. Some things they helped us do were not obvious in their documentation or UX, so it is worth a chat with them.