Post reply

Alternative for stored procedure versioning (for grouping)

  • October 5, 2006 at 7:24 am

    #69253

    I have a question about versioning stored procedures:

    I use sp versioning to group procedures together so I don't have to create branches that affect the performance of the sp (execution plan calculation).

    For database synchronisation, we use Red Gate's SQL-Compare.

    SQL-Compare raises errors when it gets to the versioned stored procedures, and there will most likely be no patch, because stored procedure versioning is 'depricated' (says Red Gate).

    Is this true, and is there an alternative way of grouping stored procedures in SQL Server 2005.

    Regards, Stefan v. Opbergen

  • October 9, 2006 at 8:00 am

    This was removed by the editor as SPAM

  • October 13, 2006 at 9:24 pm

    #665876

    I'm not sure what you mean by "grouping".

    I suppose you could group sprocs by putting them in different schemas. For example, if you have a set of HR related sprocs, put them in the HumanResources schema, and so on.

    There are these topics in BOL about hooking up SQL Server 2005 tools to source control (I assume that's what you mean by versioning):

    http://msdn2.microsoft.com/en-us/library/ms174172.aspx

    http://msdn2.microsoft.com/en-us/library/ms173550.aspx

    and here's an article that talks about a quick and dirty way to setup versioning on sprocs. It's not really source control, but it's better than nothing:

    http://www.sql-server-performance.com/rd_sp_text.asp

    ---------------------------------------
    elsasoft.org

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply