one problem is that linqtosql (L2S) is now legacy -- linq to entities (L2E, part of the entity framework, EF) is the preferred choice for future compatibility.

Manuel5/20/2009 2:38:53 PM

Marco, thanks for your comment. Here's Dino Esposito's reply:

"The reader is right when he says that most of the time T-SQL statements written by programmers are the main cause of troubles. However, the challenge (and complexity) of modern software require that developers work with object models thus raising the abstraction level from physical to a more conceptual view. O/RM tools (LINQ to SQL is just one of the simplest) serve this purpose and may generate T-SQL code. Or they can be programmed to invoke stored procedures written by DBAs.

I also suggest that DBAs learn more about modeling techniques and O/RM tools. O/RM tools (including LINQ to SQL) offer a mapping layer where bindings between object properties and tables/columns are made. This mapping must be the realm of DBAs; the model must be the realm of developers/architects."

Anne5/12/2009 11:01:08 AM

It could be a stupid thought, but isn't it easier let a DBA write the T-SQL statements? Just keep the presentation's programmers doing what they do best (Good and useful interfaces). During my DBA carrer I noticed that 99% of the problems are caused by the poor design, most of it done by programmers.

Marcos5/4/2009 10:10:08 AM