Entity Framework Overkill?

Question

So I have a project and we have some data access requirements. This is fairly simple, we just want to retrieve data returned from a stored procedure (this already exists) and update a couple of tables. My options I guess are to:

• Write a bespoke Data Access component that could be used on other projects as well
• Use Microsoft's Enterprise Library Data Access Application Block - however, as the source is Oracle and would want to use ODP this may also need to use the Enterprise Library Contrib?
• Use an ORM such as Entity Framework
• Other alternatives?

I am leaning towards option 2, although it seems I would also need to use the Contrib? I am thinking there isn't much benefit of using the Entity Framework for a fairly simple solution such as this, particularly when having to integrate with SPs?

Or am I missing something?

Thanks

Answer 1

is the stored procedure and tables all in the same oracle db? If so why not just write a bit of pl/sql?

Answer 2

I would put serious thought to using a micro-ORM such as dapper, massive, Simple.Data, peta-poco etc. this makes it easy to call the procs and process the grids, without the complexity and overhead of a full ORM. I know dapper works with both oracle and procs.