February 5th, 2014, 12:55 PM
Source Control (TFS) for database objects
I've been trying to figure out the best way to handle source control and figure I'll ask others and see what they're doing.
Currently we use TFS for our source control of all C# projects. When we change any database objects (stored procs, etc.), we just go into sql and make the change on a development server. The dba's then move the code from the development sql server to qa, prod, etc.
We'd like to incorporate our sql code into tfs.
So, let's say a developer is working on a c# project and needs to modify a stored procedure. Would he create a visual studio database project and script that stored procedure into the project? I've read about visual studio database projects and it seems it's "recommended" to have a c# project and database project together in a visual studio solution.
How are you handling this at your company?
Click Here to Expand Forum to Full Width
This is a CodeGuru survey question.