Hi Raoul,
I am sorry that you are experiencing issues.
In general, we are aware that working with diagrams that contain a large number of classes results in high resource consumption. The cause for this, however, lies in
DSL itself (the technology for building modelling tools in Visual Studio). Nevertheless, you can drastically improve the situation with the help of the next two approaches:
Approach 1: Changing the mapping approach to Fluent (code-only) mapping
The problem will permanently disappear if you re-generate the model with the help of
the New Fluent Model wizard. It will produce for you all the necessary classes (persistent classes, metadatasource, context) and from that point on you can modify the model through the
Fluent API. Additionally, any changes you do in the model can be persisted to the database with the help of the
UpdateSchema method. With this approach
you will not have an .rlinq in the project at all.
Approach 2: Logically separating the diagram into multiple diagrams
The
multiple diagrams feature of Data Access allows you to separate the big diagram to smaller chucks, but to keep all of them in one .rlinq file. This way you preserve all the constraints and navigation properties. Additionally, when you open the .rlinq file, Visual Designer will initially draw only the default diagram. If you need to review any of the other diagrams, you can do it from
Model Object Explorer.
I hope this helps. Let us know if you need further information or assistance.
Regards,
Doroteya
Telerik
OpenAccess ORM is now
Telerik Data Access. For more information on the new names, please, check out the
Telerik Product Map.