I use VSS in a sort of "disconnected" or "stand-alone" mode. I place my .sql scripts (for both SPs and DDL) in various folders under my project, and check them out/in as needed using the VSS client interface. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=
I'm not sure I know what you mean by "force it on to other users".
If you mean force them to check it out/in of VSS, rather than just go directly to the database and overwrite what is already there, I can't think of a way to do this.
In many shops, there is only one (with an alternate) person who actually runs the scripts against the database. The other developers check the code out/in of VSS, and request the designated DBA run their changed scripts against the database in order to create the new SPs or add or modify the tables.
There are many bonuses to this approach, including being able to "version" your entire database.
The obvious disadvantage is a bit more beauracracy. [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=
Yeh I meant force them to check it in/out, unfortunately I work in an environment where there are 6 of us working on the same app and the time issues of passing a script to a DBA have forced us down the 'Free for all' road.
I feel your pain, Bigley...there just isn't an easy AND hassle-free solution (at least none that I can think of). [sig]<p>Robert Bradley<br><a href=mailto: > </a><br><a href=
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.