Data Access Strategies

I had interesting conversations with a number of people about different data access/ORM strategies at MIX recently and was trying to understand where people are spending their efforts in consuming data. The conversation was essentially a discussion of who is using what to access data in .NET applications. I had assumed that certain solutions were widely used and others were not but I didn't have a good idea of what the market was really like. To help me with this I am asking you (my readers) to share with me where you are investing time in data access by taking the following poll:

Comments:

I'm using also dOOdads (now they made EntitySpace)

I've used the Data Access block within Enterprise Library at times in the past.

Excellent idea to put this poll. Few years ago my team was deciding what data access method to use and I think this poll would help at that time.

Tnx
Petar Repac

Petar,

Most Used != Best...its not a popularity contest...I am trying to determine who is using what and how that impacts our industry.

Shown,

I agree with you, but at minimum it is a list that should be considered when deciding on data access strategy.

I am aware that everything must be put in context. Data access method for small single user app could be wrong for enterprise application.

Well, we choose typed datasets for enterprise application framework and today it seems to me we could chose better.

BTW, how would you determine WHO is using what. The poll will just give info on what is used, but not WHO (by that I mean the context, i.e. database independence, number of users, concurrency, ....).

"Other"/"Custom" would be my pick but only because the one use case I have in my head values a common model across all SOA/multi-tier pieces backed finally by stored procs rather than on sheer mapping or querying prowess. I have not seen anything (for non-$$$) that really targets this.

Currently using Typed & Untyped Datasets, iBatisNet, some custom DAL classes; plan on using LINQ to everything and the ADO.NET Data Services / Entity Framework.

Also using custom DAL based on DataReader (not DataSet) and ExecuteScaler... built from Microsoft DataAccessBlock


 



 
Save Cancel