Feedback
Did this article resolve your question/issue?

   

Article

Creating a Connect for ADO.Net data model may take a long time

Information

 
TitleCreating a Connect for ADO.Net data model may take a long time
URL NameCreating-a-Connect-for-ADO-Net-data-model-may-take-a-long-time
Article Number000185057
EnvironmentProduct: Connect for ADO.Net
Version: All Supported
OS: All Supported
Database: All Supported
Application: N/A
Question/Problem Description
Creating a Connect for ADO.Net data model may take a long time. What causes the entity data model generation to take so long?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
The most common cause for the generation of an entity data model to take a long time is based on the number of objects in the database that the user has access to.  It also depends on the relationship between the objects.  Associations such as foreign keys may require more processing and thus more time to generate the model.
Resolution
Ideally, once the data model is created, it will rarely need to be regenerated as this process is only needed when a change is made to the objects in the database.  

Where possible, restrict the number of objects the user has access to. However, this may not always be an appropriate option.
Workaround
Notes
Last Modified Date5/11/2016 5:41 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.