fmuzul (3/11/2013)
...Maybe you live in a different world than mine. For me the redeploy of an application is not a problem, I just need to replace a .exe file, and this can happen automatically also (as many modern applications do, checking for an update somewhere into the net). Updating the code of a stored procedure could be more uncomfortable.
...
Or yes, I do, very different world, actually!
The change deployment of systems I do usually work with, requires more than one .exe file replacement. They kind of consist of many of executables and DLL's ;-). Also, quite often changes related to system database (or quite often, databases) include not only change of some queries, but also database structural changes and data transformations. Therefore change deployment of database is still required (and better to be version controlled too).
What exactly makes T-SQL code change in stored proc more uncomfortable then c++ or c# or any other code change in your application?