sql server (alternate): Hi
Is it possible to use Visual Source Safe with SQL Server in
order to keep track of all modifications done to stored procedures?

What are the pros and cons ?

I use it in a way, by generating a create script for my database and
checking that in ("check out from sourcesafe, set to writable, generate
create script over it, check it back in again"). Sucky but works for me.

[quoted text, click to view]

[quoted text, click to view]

http://groups.google.ch/groups?hl=en&lr=&q=vss&btnG=Search&meta=group%3Dcomp.databases.ms-sqlserver

Simon

Eugene (ygorelik20@hotmail.com) writes:
[quoted text, click to view]

Of course. Just like any other source code, you check out, edit, test and
when you are done you check in. You may find it simpler to use a third-
party editor like Textpad or UltraEdit for editing. From such editors
you can typically invoke a command-line tool, so that would be how you
would load the procedure into SQL Server.

There are several advantages with using these editors:

o They are better editors that the SQL Server tools.
o Since code hits the disk before the server, you know that what you
tested is what you check in.
o You can easily set up SourceSafe so that all files opens in your
editor. Right-click Edit and it's there!


[quoted text, click to view]

Version-control is essential in any serious software development. So
the question of cons is not relevant.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at

We do the same with VSS. For each SQL project, I have the following
folders.
1. Tables
1.1 - table scripts (Create ONLY)
1.2 - Triggers
1.3 - Constraints/defaults/indexes/PK/FK

2 - Views (Drop & Create - No Alter)

3 - Stored Proc (Drop & Create - No Alter)

4. - DTS (Even though SQL server handles Version control this is just
for completness

5. - Jobs, and other admin scripts.

6. - Test scrips such as data modifications and load scripts.
Hope this helps...!