Re: Help with SQL 2005 and Sourcesafe 6

Thanks for your reply. One thing with VB code is that once you have checked
it in, the code is not compiled, but it is the latest version. That doesn't
seem to be the case with stored procedures. My question is if you have your
scripted stored procs in VSS, do you then have to, say, run an alter script
@ the end of the day which updates the databases stored procs with the
modified procs from VSS?

Appreciate your time.


"Erland Sommarskog" <esquel@xxxxxxxxxxxxx> wrote in message
news:Xns98C1F402F4B7EYazorman@xxxxxxxxxxxx
Nomad (nonsense@xxxxxxxxxxxxxx) writes:
Thanks very much for the reply. If the stored procedures are in the
database and also SourceSafe, when checking the stored proc back in,
would that update the stored proc in the database, or do you just simply
update it manually, when deploying it?

If you check in a piece of VB codes does that also compile the VB
code?

Checking-in and updating the database are two different things. SourceSafe
does not even know about the database. Nor should it. From a version-
control perspective there is no *the* database. Shipping is something
you typically to do many places.

I don't think I've mentioned it, but you can set up integration with
SourceSafe in Mgmt Studio. I know I played a little with it during the
beta, but I've forgotten the details. Personally I have never liked
the various integration features, be it VB or whatever, but I prefer to
work directly in VSS Explorer.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx


.

Relevant Pages

  • Re: Why cant recursive queries contain...?
    ... Triggers would be events, stored procs would be functions, views would be linq statements, tables would be collections etc. Imagine writing your application in C# and stepping through code and straight into a C# stored proc ... You can definitely use C# as a front end for a database; in fact, people do exactly this every day when they write .NET Windows and Web client applications. ... C# would probably make a better native language for an object-oriented database as opposed to a database derived from the relational model though. ... "Expert SQL Server 2008 Encryption" ...
    (microsoft.public.sqlserver.programming)
  • Re: Encrypting SQL objects
    ... objects, i.e. Stored procs, Views, triggers. ... engine must be able to read the source code at run to be able to compile ... And if SQL Server has access to it, ...
    (microsoft.public.sqlserver.security)
  • Re: major security concern - any sql user with minimal permission can see code for all stored procs
    ... remove select access (and execute access on selected stored procs in the ... things - and hence has enterprise manager - then this approach won't work. ... If you just want to lock down a database, then I'd try my approace - lock ... >> connected from a remote location to my SQL server at port 1433, ...
    (microsoft.public.sqlserver.security)
  • Conversion between Access 2002 and 2003 only via 2000?
    ... I've been developing an Access database with a SQL Server backend. ... it crashes. ... access and compile the code in A2003. ...
    (microsoft.public.access.conversion)
  • Check syntax of stored procs and views-sp_grep
    ... Does anyone know of a good way to check the contents of stored procs and ... views within a SQL Server 2000 database for key words? ...
    (microsoft.public.sqlserver.datawarehouse)
Quantcast