I'm heading for Helsinki at the moment to deliver another Workshop on SQL Server 2005 (formerly known as SQL Server Yukon) so I have some time to reflect on the previous deliveries of this workshop.
The topics that I'm delivering myself are the developer related topics. One could categorize them as follows:
The most loved topic is without any doubt the Yukon CLR.
The topic adored by some while invoking a big yawn from others: XML Integration
The most wrongly ignored topic: T-SQL improvements
output inserted.idvalues (x,y)
The most debated topic: Objectspaces
This is a real hot debate. Java developers have this debate and now I’m afraid Microsoft developers will have the debate as well. I know it’s not a SQL Server Yukon only topic but it’s hard not to discuss data access when talking databases.
· My take: a good designed DAL and framework can be as efficient as an Object Relation Mapping Framework. Optimizing data access when using an OR Framework will be a challenge or will require effort comparable to building a proprietary DAL in many cases. I would only use frameworks like this if:
o There’s a lot of business logic running on the server with little user involvement
o I need to build an app on a database I don’t own with a very complex schema (let’s take SAP as an example).
o My boss tells me to
· Some ISV’s take on this:
o Way cool! Every SQL statement I don’t have to write is saving me money.
o Hey, I wrote this already years ago!