Key Reports Change Control

Cinruskin

Greetings,
We have a requirement to lock down any objects that are used to create Key Reports for our accounting department. We purchased SQL Source Control with the belief that this would allow us to lock down the objects in question and then, in the future, track any changes that we make to tables, stored procedures, or views. The databases in question are production databases, and we noted in the instructions for SQL Source Control, that Redgate advises that it not be used on production databases. This leads me to the two questions I have: 
1. Surely other people have the same requirement to lock down and track any changes made to production databases. What tools or procedures do they use?
2. Are there any instructions on setting up SQL Source Control with Azure DevOps for change management?

Thank you!

Sergio R

SQL Source Control is a tool meant to facilitate development within a team of SQL Developers.

By linking your databases to a Version Control System, you can keep a revision history of all the objects and revert easily to a previous version if needed.

SQL Source Control can be used with SQL Change Automation  to manage your releases, this tool integrates with Azure DevOps.

Please see the following for more information on how SQL Source Control and SQL Change Automation can help you:
https://www.red-gate.com/hub/university/sql-change-automation-with-sql-source-control-projects