I’ll be doing a one-day workshop on SQL Server 2005 in Amsterdam in June, as a postconference event of Microsoft DevDays. Although I’ve done quite a few events on SQL Server 2005 before, this one will be quite a bit different from any that I’ve done before. It deals with best practices.
It’s been about 4-5 years since I started teaching and working with early adapters of technologies like SQLCLR, Service Broker, and XML data types. During the “break in” period, people were most interested in how they worked, syntax and semantics. Now that we’ve had a while to practice, folks are wondering how its working out. Did these revolutionary technologies change the database landscape?
I’ll begin the workshop by discussing the impact of items like statement-level recompilation, SQL algebrizer and plan caching changes, plan guides, plan forcing and the like have had on the way people write procedural code. The effect of snapshot isolation on how people approach locking issues. And go from there into the uses and guidelines for features, like Service Broker, that folks normally associate with “SQL Server 2005 change”. With some real-life examples. It’s a different outlook that will benefit you even if you’re not on the bleeding edge. And because some ‘next generation’ features will be introduced at TechEd the precededing week, I’ll answer questions on where I think we go from here.
Also not to be missed: Dino Esposito will be presenting an excellent workshop on Ajax next door.
See you there.