Re: SP Source Control Options

From: Erland Sommarskog (sommar@algonet.se)
Date: 02/24/03 

From: Erland Sommarskog <sommar@algonet.se>
Date: Sun, 23 Feb 2003 23:11:33 +0000 (UTC)

[posted and mailed, please reply in news]

Guy (Guy_Schuler@Kumtor.com) writes:
> I am new to an environment (located in Central Asia) that
> relies heavily on Stored Procedures on SQL 7. It is clear
> that many of the problems we experience are from poor
> update and recovery controls of these SPs.
>
> What options are there to implementing Source Control on
> MS Stored Procedures?

Script them out of SQL Server, using Enterprise Manager. Opt for
one object per file. Then add the files to your favourite source
control system. From then on, let the version-control system be
your one and single truth. That is developers that change stored
procedures without checking them out, should be whacked on the
fingers.

If you are using SourceSafe, you can add this line to you SS.INI:

  .SQL = C:\MSSQL7\TOOLS\BINN\ISQLW.EXE

and then right-click edit in VSS Explorer will open the file in
Query Analyzer.

In our shop we use a third-party editor from which we invoke our
or load tool (but you could use command-line ISQL as well). The
nice thing with this is that what goes into the database, first
hit the disk. Using QA, there is always the risk that you forget
to save. 

-- 
Erland Sommarskog, SQL Server MVP, sommar@algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

Relevant Pages

  • Re: SP Source Control Options
    ... > relies heavily on Stored Procedures on SQL 7. ... > What options are there to implementing Source Control on ... Script them out of SQL Server, ... control system. ...
    (microsoft.public.sqlserver.security)
  • Re: Identity Column
    ... Especially when proper error handling tells me which stored procedure ... So you're saying if I use stored procedures I can't refactor, ... avoiding stored procedures and dumping all of your ad hoc SQL in the data ... You get full refactoring, source control, revision ...
    (microsoft.public.sqlserver.programming)
  • Re: Setting Encryption to 1000 Stored procedures
    ... If you don't have your stored procedures on disk and under the version ... adding WITH ENCRYPTION, it may be simpler to have all in one file. ... control system of your choice. ... Note also that if you start to change procedures in SQL Server without ...
    (microsoft.public.sqlserver.security)
  • Has anyone used SQLSourceSafe?
    ... many SQL objects (tables, stored procedures, user defined functions, views, ... We're going to look into a number of tools to help with SQL version control, ...
    (microsoft.public.sqlserver.server)
  • RE: SQL SERVER 2000 Integraion
    ... It will integrate with stored procedures. ... how it can provide version control for user defined functions. ... > control on my Store Procedures in SQL 2000? ... > SQLSERVER? ...
    (microsoft.public.vstudio.sourcesafe)