Currently there are two developers working on a VB.NET desktop application that accesses a number of SQL Server databases. We have recently added SQL Server script files (for stored procedures, tables, agent jobs, views and functions) to SourceSafe
(VSS). This finally gives us a way to store sql source code with change tracking, centralized shared access, etc. - a vast improvement over the previous method of manually trying to keep track of all the code components of our database development
We have a "solution" defined in SQL Server that has three projects: right now we have one project for each of three databases that we are accessing. The projects were created as "SQL Server Scripts" so they have Connections, Queries and Miscellaneous
folders. The Queries folders currently contain stored procedures used in each of the three databases. In all we have about 200 stored procedures.
However, we have not yet figured out a bullet proof way to keep the source in VSS in sync with the code that SQl Server is actually storing and executing. If I open a stored procedure for edit by double-clicking the file shown in the Solution frame, it gives
me the stored procedure in VSS. If I edit it and then click on EXECUTE to actually ALTER the procedure in SQL Server and then check-in the
View Complete Post