This question is locked. New answers and comments are not allowed.
Donald Norris
Top achievements
Rank 1
Rank 1
Donald Norris
asked on 07 Mar 2011, 06:23 PM
I have the same fundamental question regarding ORM as I do with Entity Framework. I have a database with 70+ tables. Should I declare one massive model with all tables, views and stored procedures or smaller ones that are more task specific.
The issues I am concerned about are memory footprint using one model and manage changes when I have many small models where a table may exist in more that more model.
Your insight into this would be greatly appreciated.
Thanks
The issues I am concerned about are memory footprint using one model and manage changes when I have many small models where a table may exist in more that more model.
Your insight into this would be greatly appreciated.
Thanks
1 Answer, 1 is accepted
0
Hi Donald Norris,
Petar
the Telerik team
Currently we do not support separating your model into different sub models and keeping them in sync with each other, however we have it in our plans for the future. As for the memory consumption I am afraid we have never did memory profiling (it is in our plans though) but I can assure you you should not have any problems with models consisting of 70-200 tables.
Best wishes,Petar
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!