Editorials

ADO, ODBC(!), LINQ to SQL Server…

Featured Article(s)
SQL Server 2005 Transact-SQL Optimization Tips (Part 1)
Here are some helpful SQL Server 2005 Transact-SQL tips.

Using LINQ to… <insert platform/technology> Yet?
I know a lot of people have been talking about the LINQ technologies and approaches to working with SQL Server. The object-oriented approach, the more integrated view of the database from the context of application development and other benefits can be pretty strong. Microsoft has also been pushing the technology, demonstrating it extensively and talking about the benefits (we have sessions on this too in the vConference this week).

My question is – are you using this yet in production systems? The reason I ask is because I was reading through this post about not only LINQ, but also entity framework – and they’re talking about big changes (to put it mildly) and challenges for LINQ and even the entity framework.

I know building out the interface layers is probably one of the most challenging things facing Microsoft in creating tools for developers. There have been a number of different approaches to this over the years (makes me sound old!) but I really think there are some solid benefits to the LINQ approach.

What types of things are you using at this level for development? "Traditional" ADO-type interfaces? Something else?

Send in your thoughts/experiences here.

Featured White Paper(s)
Whole Server Protection from a Single Solution
The complexity of traditional recovery solutions compounds an already difficult situation, and heightens the opportunity for … (read more)

EMC Long Distance Recovery for SQL Server 2005 Reference Architecture
Read Long Distance Recovery for SQL Server 2005 and learn about this data recovery solution which was developed in partnershi… (read more)