Author Topic: SQL Server Implementation - Database Connections  (Read 915 times)

3dot14lot

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
SQL Server Implementation - Database Connections
« on: January 15, 2008, 12:30:23 pm »
Hi,

We are planning on implementing a SQL Server repository for EA (version 6.5) for the first time. We can implement this on a server dedicated to EA or implement in our "shared" environment (by shared I mean the SQL Server database engine is shared by mutliple applications of which EA would be just one). Our Ops folks are concerned with performance resulting from one database connection dedicated to each EA user, and the potential for that to impair performance in the shared environment. Dedicating a server to EA mitigates this concern, albeit at a higher cost.

Does anyone know how EA handles database connections? Does it act like a typical "fat client" app opening a connection that is dedicated to that client until the EA client is closed?

Thanks.

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: SQL Server Implementation - Database Connectio
« Reply #1 on: January 15, 2008, 09:26:46 pm »
We use a chared server (SQL2005) and EA has no effect on other applications (none that we have noticed).
And we have a rather big model.
Recursion definition:
If you donít understand the definition read "Recursion definition".

3dot14lot

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: SQL Server Implementation - Database Connectio
« Reply #2 on: January 16, 2008, 04:48:18 am »
Thanks Martin. Approximately how many EA users do you have?

Martin Terreni

  • EA User
  • **
  • Posts: 672
  • Karma: +0/-0
  • Sorry, I can't write
    • View Profile
Re: SQL Server Implementation - Database Connectio
« Reply #3 on: January 16, 2008, 08:03:24 am »
30
Recursion definition:
If you donít understand the definition read "Recursion definition".