EAV vs XML in SQL Server 2005/2008 and LINQ

Question

I am considering the use of an EAV table in SQL Server to store some hierarchical/structured data, all the while knowing the capabilities of XML in SQL Server. I am aware of some of the performance draw backs of EAV due to excessive joins, however, does client side LINQ to object solve any of these problems?

I am looking for some advice and caveats to be aware of when considering either approach.

Answer 1

Check out:

Five Simple Database Design Errors You Should Avoid

and look at section (3) Entity-Attribute-Value Table

Basically: don't do it. Even if you use Linq-to-SQL to "undo" some of the messiness of EAV - I personally just wouldn't even start using it. It'll be messy some day, sooner or later.

Marc