Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Meet the Buffer Cache

I realize that most hard-core backenders will already know most of this but, with all of the posts that have entered my aggregator relating to sprocs and ad-hoc sql, I thought that I'd take this opportunity to add a link to an article I wrote a few years ago which discusses what gets cached (and when):

http://www.msdnaa.net/Resources/Display.aspx?ResID=825

(Listening To: Out of the City (Hardkandy Mix) [2 Heads / Chillout Sessions Vol 4 (Disc 2)])

1 Comment

  • "We also touched on the fact that Stored Procedures can help us to modularize our programming by storing chunks of database logic in the database rather than in our programs."



    This for me is the number one reason to use sprocs-- and it's a point that gets left out in these arguments over dynamic vs CRUD sprocs.



    With sprocs... business logic can be altered on the server without any recompilation and redeployment-- as long as the parameters are left alone, of course.



    But as to the CRUD... why do you have to have 3 people writing these things and breaking code and causing terror and confusion? If you write a code generator... you can output your CRUD script and a class library for calling them every time your structures change. Hand the class to your developers... and VS.Net shows them where the application is broken with a stack of Tasks when they switch it out.



    Any additional logic can be added to the CRUDs-- and I think this is easier to maintain than triggers.



    The bottom line: the more logic that's moved to the server, the more centalized and streamlined the maintenance becomes. And the sp's are available to anyone that can talk to the database.



    Anyways, thanks for the balanced and insightful article.

Comments have been disabled for this content.