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.