DAAB 5.0 or LinqToSQL

Topics: Data Access Application Block, Enterprise Library Core
Feb 22, 2011 at 5:49 PM

I'm starting a new project and I'm not sure what technology to use. I am between DAAB 5.0 and LinqToSql  (due to restrictions of the project I can not use the Entity Framework)

My question is which should I use?

Feb 23, 2011 at 12:32 AM

Here's my personal take on this, if you need database-agnostic features, go for DAAB.  I also read that DAAB is faster than LINQ to SQL.

If you need designer and code generation features , LINQ to SQL gives you these.


Sarah Urmeneta
Global Technologies and Solutions
Avanade, Inc.

Feb 23, 2011 at 12:29 PM

Don't use Linq to SQL.

The Team that developed this technology doesn't exist anymore.

Use instead ADO.Net Entity Framework 4.0, if you want to use something similar - thats where most of the Linq2SQL developers gone.


Feb 23, 2011 at 12:41 PM

I was also inclined to think of this but since I'm really not updated with what happened to LINQ to SQL, I did some research and found these articles talking about enhancements made for it in 2010.




Sarah Urmeneta
Global Technologies and Solutions
Avanade, Inc.

Feb 24, 2011 at 7:26 AM

Thank you for your replies, finally i decided by DAAB

Feb 24, 2011 at 9:01 AM

The deciding factor is what style of database access you want. Are you comfortable with raw ADO.NET - DataSets and DataReaders, Command objects and connections? If so, DAAB makes that kind of programming much more convenient.

On the other hand, if you want to work in terms of your object model, and have a tool that will automatically map from your object model to relational schema and back, then look at something like Linq2Sql or EF (or nHibernate, or LLBLGen, or Subsonic, or any of the many ORM solutions out there).