M
Maurizio Coffinardi
Hi,
I'm developing an ASP.NET application and I'm going to use ADO.NET Entity
Framework. The underlying database contains almost 800 tables.
Do you think I can create just one data model with all the tables and
relationships or the best way is to split it in more .edmx files?
Thinking about performances I thought to choose the first option but it's a
bit hard for me to do it because every table is directly or indirectly
related with the other tables and I don't know where "to break" the data
model.
Any suggestion?
Thank you.
I'm developing an ASP.NET application and I'm going to use ADO.NET Entity
Framework. The underlying database contains almost 800 tables.
Do you think I can create just one data model with all the tables and
relationships or the best way is to split it in more .edmx files?
Thinking about performances I thought to choose the first option but it's a
bit hard for me to do it because every table is directly or indirectly
related with the other tables and I don't know where "to break" the data
model.
Any suggestion?
Thank you.