Comments on: It’s all code http://blog.gdinwiddie.com/2007/07/30/its-all-code/ Effective software development Thu, 20 Nov 2008 19:48:03 +0000 http://wordpress.org/?v=2.0.6 by: Agile Jedi http://blog.gdinwiddie.com/2007/07/30/its-all-code/#comment-27445 Sat, 29 Mar 2008 19:29:52 +0000 http://blog.gdinwiddie.com/2007/07/30/its-all-code/#comment-27445 I never discount Stored Procedures but we try to avoid them because it just adds another layer of stuff to keep track of. What really surprises me is that you have people working on the LIVE database. Wow! This is an old post so I can only hope that you have been able to convince your team to implement better configuration management. I never discount Stored Procedures but we try to avoid them because it just adds another layer of stuff to keep track of. What really surprises me is that you have people working on the LIVE database. Wow! This is an old post so I can only hope that you have been able to convince your team to implement better configuration management.

]]> by: Richard Lawrence http://blog.gdinwiddie.com/2007/07/30/its-all-code/#comment-10282 Fri, 17 Aug 2007 01:12:02 +0000 http://blog.gdinwiddie.com/2007/07/30/its-all-code/#comment-10282 I agree, stored procedures aren't the problem. In fact, in the Microsoft world where I work, nobody debates stored procedures any more; they're just a given. I think it's a problem of treating the database different from the rest of the application. When I coach teams, I try to help them get their database scripted and in source control and part of the automated build so that (1) it's clear what version of the database goes with what version of the code and (2) a fresh database can be built to any version in a minute or two with one click on a developer machine or on a build/test server. I'm still not happy with the tooling around SQL scripts, whether stored procedures or other DDL, but this approach at least solves the problems you're having. BTW, I appreciated your contributions in the sessions we were both in at Agile 2007 this week. Never got a chance to meet, but hopefully will at AYE. Best, Richard I agree, stored procedures aren’t the problem. In fact, in the Microsoft world where I work, nobody debates stored procedures any more; they’re just a given. I think it’s a problem of treating the database different from the rest of the application. When I coach teams, I try to help them get their database scripted and in source control and part of the automated build so that (1) it’s clear what version of the database goes with what version of the code and (2) a fresh database can be built to any version in a minute or two with one click on a developer machine or on a build/test server. I’m still not happy with the tooling around SQL scripts, whether stored procedures or other DDL, but this approach at least solves the problems you’re having.

BTW, I appreciated your contributions in the sessions we were both in at Agile 2007 this week. Never got a chance to meet, but hopefully will at AYE.

Best,

Richard

]]>