The source-control tag has no wiki summary.
3
votes
5answers
289 views
Stored Procedures under Source Control, best practice
I am currently using Tortoise SVN to source control a .NET Web Application. What would be the best way to bring our SQL Server stored procedures into Source Control? I am currently using VS 2010 as my ...
0
votes
1answer
128 views
Deploying to an existing database from VS 2010 on TFS
I am trying to find a way in VS2010 to add a few objects to an existing database without scripting out all of the existing objects. This is a maintenance project that is adding a table, altering an ...
3
votes
2answers
63 views
With the advent of integrated source control, do stored procedure changes still need comments?
Back in the old days, my team had a policy that any stored procedure modification required comments in two places:
Top of the stored procedure with an overall summary of the changes
made
Comments ...
1
vote
2answers
58 views
Consolidating data changes in SQL Server by team
What is a good way to manage developers' data changes?
I am using RedGate SQL Source Control to monitor changes to tables and stored procecures, so that when we do a production build, I can include ...
4
votes
1answer
2k views
TFS2010 for SSMS 2012
SSMS 2012 does not work with VSS 6. We installed modern source control, TFS 2010 server.
Then I Installed Team Foundation Server MSSCCI Provider 2010.
However the only choice for Source control ...
9
votes
7answers
659 views
Version control for database objects
The database our developers are working on is too large (have a lot of database objects). We have to control db objects changes (change management). Our company cannot have a person who would be ...
6
votes
2answers
2k views
How to extract Procedure, Function, etc. Source Code from an Oracle Export
I have generated an EXPDAT.DMP file of an Oracle database with the command:
exp userid=usr/pass@db owner=own rows=n compress=n
I then ran the following command to generate a file containing the ...
22
votes
4answers
813 views
Is there a “best-practices” type process for developers to follow for database changes?
What is a good way to migrate DB changes from Development to QA to Production environments? Currently we:
Script the change in a sql file and attach that to a TFS work item.
The work is ...
