When opening the EntitiesModel.rlinq in my project it takes minutes (not seconds, minutes!) before the diagram is displayed in vs2013.
The database -SQL 2012- is moderately complex with 176 user tables and 1314 constraints (PK/FK). At first I thought the high cpu utilization and slow (re-)generation occurred because the model was generated some open access versions earlier and updated with each subsequent release.
Today I created a new project and recreated the model, but it is still extremely slow. When creating (or updating) from database the cpu rises to 100% and visual studio is non responsive. I've tried fluent, sperate files, xml or attributes in any possible combination but to no avail... Generation and updating are painfully slow. Just adding/changing columns to existing tables takes to much time updating the model from the database. Productivity grinds to a halt and I there's only the coffee machine to calm my frustrations at that point...
So my question(s) are:
- Could I break up the single model to smaller models, preserving FK relations "over the models". E.g. If tableA is modelOne and tableB is in modelTwo can I keep using "tableA.tableB" / "tableB.tableAs"?
- Could it be a database issue? Tables are created straight forward with a single PK (Guid) and multiple FK's (also Guid). No indexes either.
- Does anyone have suggestions on speeding up the (re-)generation of my model?
It's just the model (re-)generation which is annoying. Other then that it does the job just fine.