Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 13, 2011 10:11 PM by claudia888
Jul 13, 2011 07:59 PM|LINK
I just started a MVC3 project and started using .edmx. Before this project we used SQL server 2005 and 2008; and we always designed the database modeling first, set the db up in sql server, then access the database from the application.
It seems that .edmx represents db generated from models; which is convenient if you don't want to do data modeling - but there's normally always a price to pay for using tools to save time, so my questions are:
1) Capaicity limit / performance - will use .edmx have any limit on the capacity or performance of the application, once the app goes to production? This app is supposed to support a lot of users, so the capacity and performance is very
2) Update and maintanence: Do we need to manually re-generate .edmx file every time the data models change?
3) Deploy to production - We still plan to use SQL server (full version) for our production environment; how do we go about deployment when we finish developing this project, in regards to how to "map" the .edmx or the .mdf (under "App_Data"
folder) to the actual sql server?
Any inputs/advices are grealt appreciated! We need to make the right decision for this project asap.
Jul 13, 2011 09:12 PM|LINK
This app is supposed to support a lot of users, so the capacity and performance is very important;
Edmx or not : if you execute "select * from table" from a 1.000.000 table, it will never be performant
3. modify the connection string from web.config
Jul 13, 2011 09:37 PM|LINK
Thanks for the reply. Please clarify your answer for 1) capacity/performance - are you saying the using .edmx will be no different than using a "normal" .mdf in a sql server, in its capacity or performance when handling a lot of concurrent users?
Also when we deploy to the full version sql server in production, will we still be using .edmx or need to somehow convert the .edmx to a normal .mdf?
In general what is the benefit of using .edmx, versus the "normal" way, i.e. setting up db in sql server to start with?
Thank you very much.
BTW - you provided answer to another post but I have a follow-up question. If you have a minute, do you mind take a look at this and give some input / advice? Thanks so much!
Jul 13, 2011 09:49 PM|LINK
Edmx does not equal MDF, the Edmx talks to the database to do data operations with the database. When you compile your app the Edmx file will become part of the application, it will not be a separate entity. The only exception would be if your Edmx file
were located in a separate project, in which case it would be compiled into it's on DLL.
The beneift of the Edmx is that it opens up the whole EF to you, instead of having to do things the old manual way.
Jul 13, 2011 10:11 PM|LINK
Thanks a lot sbrauen!