Is there a alternative for EF in MVC4

Question

0.00/5 (No votes)

See more:

I have a project with more than 1000 tables in sql database. I am using MVC4 and I do not want to use Entity Framework as my project will frequently use CRUD operations. Suggest an alternative for Entity Framework.

Posted 5-Dec-13 10:11am

Member 10447901

Add a Solution

Comments

Sergey Alexandrovich Kryukov 5-Dec-13 16:20pm

This does not look like a sound motivation of not using EF. Also, if you are asking for alternative, you should explain what would you expect from it, something which is supposed to be better then EF, depending on what do you want to achieve...
—SA

sudhir chand 5-Dec-13 16:35pm

The performance goes down as the number of tables increases.

Sergey Alexandrovich Kryukov 5-Dec-13 17:17pm

Understood. Hope Solution 1 gives you the idea. By the way, noSQL looks promising, but it all depends...
—SA

Zoltán Zörgő 13-Dec-13 11:41am

Any progress?

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Zoltán Zörgő** · Answer 1 · 2013-12-05T10:30:00

EF is an ORM. There are many ORMs for dotnet. You can start here: http://en.wikipedia.org/wiki/List_of_object-relational_mapping_software[^] (section .net). But you can also google for it, because there are more - many more.

But if you are afraid of any performance issues because of the large table number (might be an architectural mistake on it's own), you can use the plain old approach (SQLCommand and it's friends). Still, I am not sure, that you really gain a lot. EF is really good, and you loose a lot on other scenes of the lifecycle by not using an ORM.

But to choose the best ORM for your needs... well, that could be a challenging task. Performance and complexity are two opposite things. You could place EF and NHybernate on one end and this one for example at the other one: ServiceStack.OrmLite[^]. But you have to decide based on your real needs.

My opinion: if you end up with 1000+ tables, you probably should look around in other data store concepts, like noSQL[^].