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