Right now we have a bunch of database servers with stored procedures running in them that are poorly documented and exist nowhere else.
When a change is made to one, there is no log, and it's really hard to figure out why something that was working suddenly fails.
We've recently switched to using proper version control using SVN, so I was hoping to add these stored procedures to version control.
We are a .Net shop, and I'm aware that there exists a Database
project type. Would that be a good approach?
Alternatively I could just keep the stored procedures as text files and operate on those, but I'm wondering about the annoying deployment steps involved with doing so.
Check out redgate's sql source control. It has an interface built into SSMS and can integrate with SVN.
http://www.red-gate.com/products/sql-development/sql-source-control/
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With