Version handling for procedures? | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Version handling for procedures?

Is there any way to apply version handling to stored procedures. I’m involved in a project where the procedures are constantly developed and its almost impossible to remember the changes that was made 3 months ago. Any ideas?
As far I know, no.
Luis Martin
Moderator
SQL-Server-Performance.com One of the symptoms of an approaching nervous breakdown is the belief that one’s work is terribly important
Bertrand Russell
All postings are provided “AS IS” with no warranties for accuracy.
You need to maintain a seperate document for recording the changes you are doing Madhivanan Failing to plan is Planning to fail
You need to use other tools to deal with version handling.
You can use Thrid part tools such as MS Visual Source Safe.
True using VSS or PVCS is the best method to keepup the version information for a database object. http://msdn.microsoft.com/archive/en-us/dnarsql7/html/sql7storprocvers.asp
http://blogs.msdn.com/korbyp/archive/2003/07/03/54046.aspx Satya SKJ
Contributing Editor & Forums Moderator
http://www.SQL-Server-Performance.Com
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Yes you do have to use the third party tool. I have used dbmaestro for sometimes. http://www.sqlservercentral.com/columnists/dasanka/reviewdbmaestro.asp —————————————-
Cast your vote
http://www.geocities.com/dineshasanka/sqlserver05.html http://spaces.msn.com/members/dineshasanka

Maybe this is what i’m looking for: http://www.sql-server-performance.com/rd_sp_text.asp
Third party tools – most of which integrate into Visual Source Safe. I’m currently beta-testing such a tool that provides versioning for procedures, views and funtions. Feel free to check it out (link in signature). Shameless plug [:I]
quote:Originally posted by lano Is there any way to apply version handling to stored procedures. I’m involved in a project where the procedures are constantly developed and its almost impossible to remember the changes that was made 3 months ago. Any ideas?

Karl Grambow www.sqldbcontrol.com
]]>