SEO

Hi,

I am trying to put SQL Server Stored Procedures into Sourcesafe as per
the Microsoft Knowledge Base article 818368, but have run into a
problem.
The web server is SQL Server 2000 running on Windows 2003 Server. The
client dev environment is Visual Studio 2003 Enterprise Developer
Edition.

I have carried out the following steps successfully:-

1. Installed Sourcesafe client tools on the Server (sourcesafe is on
another server)
2. Run the MSSQLServer service under a domain account that has Read
and Write access to the Sourcesafe database.
3. Added the above user to Sourcesafe using the Administrator tool.
4. Installed the VS6 Stored Procedure Version Control components on
the Server
5. Enabled Version Control for Stored Procedures on the client

However when I right-click on the Stored Proc node in Server explorer
I do not get any of the Sourcesafe menu options. They are not greyed
out, they are simply not there!

Any help would be appreciated.

Alternatively if anyone has recommendations for other strategies or
other tools to use for this purpose than Sourcesafe then this would
also be welcome

Karl

Karl (karlbutcher@gmail.com) writes:
> I am trying to put SQL Server Stored Procedures into Sourcesafe as per
> the Microsoft Knowledge Base article 818368, but have run into a
> problem.
> The web server is SQL Server 2000 running on Windows 2003 Server. The
> client dev environment is Visual Studio 2003 Enterprise Developer
> Edition.
>
> I have carried out the following steps successfully:-
>
> 1. Installed Sourcesafe client tools on the Server (sourcesafe is on
> another server)
> 2. Run the MSSQLServer service under a domain account that has Read
> and Write access to the Sourcesafe database.
> 3. Added the above user to Sourcesafe using the Administrator tool.
> 4. Installed the VS6 Stored Procedure Version Control components on
> the Server
> 5. Enabled Version Control for Stored Procedures on the client
>
> However when I right-click on the Stored Proc node in Server explorer
> I do not get any of the Sourcesafe menu options. They are not greyed
> out, they are simply not there!

That's probably a good thing.

There is a serious flaw with the process outlined in that KB article.
As I understand it, checkins will be performed by the user under which
SQL Server runs, and not the actual user. This is completely unacceptable.
Note also that what this method does, is to check in disassmbled code. True,
the "assembling" consists of slicing the text into 8000 long pieces in
syscomments, but nevertheless. Finally, a shortcoming is that you cannot
version-control tables this way.

So how to do it? There are a couple of third-party tools, but I have not
investigated them. In our shop we simply use VSS Explorer to check things
in and out. The stored procedures, tables etc are simply text files just
like any other source code. We don't use VS for SP editing, but instead
we use Textpad (www.textpad.com), a third-party editor, with no
particular SQL support. But it's a better editor than Visual Studio in
my opinion. To load the procedures we fire a command-line tool from
Textpad. In our case the command line tool is a homebrew with quite some
bells and whistles. (Available as freeware on http://www.abaris.se/abaperls)
But you could use OSQL instead.

Of course you could still edit in VS .Net and use VSS Explorer to check
in out. At least if VS .Net supports saving SQL files to disk.

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

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp