We have a coding standards document that contains standards for SQL.
In the last sprint, there were some standards that were missed by the Developer, and also missed by the Reviewer.
We just had a meeting where some folks thought adding a checklist document to every ticket tagged with "SQL" would give the Reviewer a bar to measure with. Some suggested adding custom fields/checkboxes to Jira (web) tickets.
Neither solution is ideal in my estimation. On previous teams, the coding standards were like an ethos that was upheld by the Application Development Manager, believed in by the team, and taught to new Devs when onboarded. The only thing tolerated was hitting the standard.
The SQL standards are somewhat new, since we just hired on a new DBA. I'm trying to understand if this is an education task, a process task, something else, or a combination.