January 10, 2006 at 12:36 pm
Hi all, I am just in the process of conducting ananlysis for my client to determine if it is viable for them to upgrade to SQL Server 2005. I have noticed in the newdocumentation that SQL Server Management Studio integrates with Visual Source Safe for version control on Stored Procedures. This will be great for checking out stored procs and editing them and checking them back in. But my question is, are they boung to the database? Meaning if they are in VSS and someone tries to edit a Stored Proc that is on the database, will source control stop them?
Thanks
e...
January 13, 2006 at 8:00 am
This was removed by the editor as SPAM
January 17, 2006 at 7:42 pm
The SPs (and any other code/objects) stored in VSS are not the copy that is executed. You must deploy whatever you have stored for it to work. You may check-in your code, and anyone who is allowed may check it out and make changes, and it can be checked back in; but it is not executed until it is deployed. It has been six or seven years since I have used VSS so I am not familar with the current product or the details of how to use it; but this response would be similar for any type of code/version control software. If you have automatic builds from your repository, I would presume that you would only build to a test host with the latest code, and only to a CM or QA host with code that had been built and "tested"... and only to a production host with code that had been both unit and system tested - and passed.
February 14, 2006 at 11:58 am
Thank you for your insight, much appreciated.
e...
February 14, 2006 at 11:58 am
Thank you for your insight, much appreciated.
e...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply