Help with SQL 2005 and sourcesafe! - 01-22-2007 , 03:21 PM
My office are currently upgrading to SQL 2005, and as part of the upgrade
process we would like to take advantage of the source control functionality.
We already use Microsoft Visual SourceSafe 6 to store our VB programs, but
we would also like to use it to store our stored procedures and views. I
have been doing some reading into how this is possible, basically by
scripting them and then adding to SourceSafe, but I was wondering how SQL
would then reference these? I gather once all of the stored procs and view
have been added, they can be removed from the database, just not sure how
SQL will know where to look for the scripted stored procs and views once
they have been deleted from the database.
I would really appreciate some help and assistance in this matter
Thanks in advance
Re: Help with SQL 2005 and sourcesafe! - 03-04-2007 , 12:52 PM
In Management Studio, go to the File menu and click New > Project...
This lets you create a new solution and/or project file, which you can
then check into VSS.
If you have VSS 2005 installed then you'll see Source Safe as an
option in Management Studio's Open Project dialogue so that you can
open a solution direct from source control. I haven't tried that with
VSS 6.0 so I don't know if it works with the earlier version.
Since you have Visual Studio projects in VSS as well then you may want
to consider creating a Visual Studio project for SQL Server instead of
a Management Studio one. Unfortunately the Management Studio solution
and project files are not compatible with Visual Studio and vice versa
("Go figure!" as they say). Also you can't create subfolders in a
Management Studio project which means that if you want to separate
different objects such as procs and tables you'll have to create
individual projects for them - not difficult but certainly irritating.
Whether you use Management Studio or Visual Studio the process is
basically the same. You can click in the solution explorer to check
out and edit and then execute your code against a connection. This
does NOT remove the need to have the same objects in the database -
it's pretty hard to develop code without a database to develop
against. What it does mean is that source control should become the
source from which you build your releases.
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online: