Book a Demo

Author Topic: Problems with Data Model - timeout expired  (Read 11563 times)

rezaTech

  • EA User
  • **
  • Posts: 21
  • Karma: +0/-0
    • View Profile
Problems with Data Model - timeout expired
« on: November 17, 2008, 04:16:46 pm »
hi
I have connected my EA with SQL Server 2005 and using 10 users simulteneously. I have a data model into which i have about 400 tables, that i imported from my database.
My problem is in the project browser when i click one table, the system takes a long time and finally says " Microsoft OLE DB Provider for SQL Server [-2147217871]. Timeout expired".
Surprisingly it doesn't happen with all the workstations. The problem occurs in only few of them.
Is there any help in this regard????

BruceTOGAF2

  • EA User
  • **
  • Posts: 74
  • Karma: +0/-0
    • View Profile
Re: Problems with Data Model - timeout expired
« Reply #1 on: July 05, 2019, 08:43:54 pm »
I am warned by Sparx Systems Forum "Warning: this topic has not been posted in for at least 120 days. Unless you're sure you want to reply, please consider starting a new topic."

Following disappointing poor performance of Sparx EA with an Oracle Sparx repository, I have done a DBMS to DBMS project transfer from Oracle to SQL Server. Sparx EA with our SQL Server Sparx repository works much faster than Oracle. I was conducting performance tests of 8 users of Sparx EA with SQL Server Sparx repository, when we experienced problems with following errors.
•   Microsoft OLE DB Provider for SQL Server [-2147217871] Query timeout expired
•   Microsoft OLE DB Provider for SQL Server [-2147467259] [DBNETLIB][ConnectionWrite (send0).General network error. Check your network documentation'
•   ADODB.Recordset [-2146824584] Operation is not allowed when the object is closed.

I will also raise this as a new topic: Problems with SQL Server Data Model - Query timeout expired

Glassboy

  • EA Practitioner
  • ***
  • Posts: 1367
  • Karma: +112/-75
    • View Profile
Re: Problems with Data Model - timeout expired
« Reply #2 on: July 08, 2019, 07:22:49 am »
You need to check your SQL server logs at the same time occurred for the client to see why it didn't respond in time.  Also this is a user forum, please don't create zombie threads.