Stored Procedures vs Dynamic SQL
I stumbled across a post by Frans Bouma about stored procs and dynamic SQL while looking around at some of the new SQL2005 features.
I've always thought Microsoft's design patterns team had it wrong with the Data Access Application Block in the enterprise library and I've been fairly sure of myself. Now, with .NET 2.0 being released and MS putting effort into LINQ etc I thought the DAAB might get a rethink, but not such luck and lately there's been a lot of noise about how it's all so wonderful. And then there are things like .NetTiers reaching a point of maturity and I start to get even more uneasy.
So I start thinking to myself maybe I'm getting it all wrong - after all Microsoft must have at least some clue about all this stuff, right? We'll I'm glad to say that the article helped my senses recover right away. I'm now more convinced than ever that tools like the AtomsFramework, NHibernate and the other O/R frameworks are the way to go.
Thanks Frans :-)
I've always thought Microsoft's design patterns team had it wrong with the Data Access Application Block in the enterprise library and I've been fairly sure of myself. Now, with .NET 2.0 being released and MS putting effort into LINQ etc I thought the DAAB might get a rethink, but not such luck and lately there's been a lot of noise about how it's all so wonderful. And then there are things like .NetTiers reaching a point of maturity and I start to get even more uneasy.
So I start thinking to myself maybe I'm getting it all wrong - after all Microsoft must have at least some clue about all this stuff, right? We'll I'm glad to say that the article helped my senses recover right away. I'm now more convinced than ever that tools like the AtomsFramework, NHibernate and the other O/R frameworks are the way to go.
Thanks Frans :-)