The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Multiple SQL COnnections
Posted: 08 Aug 07 12:56 PM
|
We are on v5.2.6 and currently engaged in upgrading to 7, but in the mean time, the users have been reporting performance issues. When we discussed this with the DBAs they discovered that there are many more database connections on the SQL server than there are users, so it appears the application is opening multiple connections to the database. Most of the connections are 'sleeping/awaiting connection'. Does anyone have any experience with this? Is there a solution other than hurry up with the upgrade?
Thank you! |
|
|
|
Re: Multiple SQL COnnections
Posted: 08 Aug 07 1:05 PM
|
| This is true, SLX does make many more connections that users. Each running session will create several connections to the database. This won't change when you upgrade either. |
|
|
|
Re: Multiple SQL COnnections
Posted: 08 Aug 07 1:14 PM
|
| I recently upgrade a client from 5.24 to 7.01. The number of DB connections created by normal usage of the application increased. It feels like it is related to view and groups. |
|
|
| |
|
Re: Multiple SQL COnnections
Posted: 08 Aug 07 2:20 PM
|
Originally posted by Ian Fitzpatrick
Does these extra connections cause any performance problems? |
|
They shouldn't too much. That is pretty typical of any modern database application. Connections are pooled because it can help performance on the application/client side. |
|
|
|
Re: Multiple SQL COnnections
Posted: 08 Aug 07 2:25 PM
|
| We have not noticed any performance issues. BTW, there are 1200+ licenses users, and we have seen 300 to 500 users connected. |
|
|
|
Re: Multiple SQL COnnections
Posted: 09 Aug 07 9:33 AM
|
Heck, 5.2.6 was faster than the newer versions of SLX.....we still have people using it and it's lightning fast compared to 6.13, 6.2 SP6 etc.
The problem was that 5.2.6 DID NOT use ADO.....and there was a limit to how many connections you could run on it......or performance suffered. The connectionS (that's like 2 -5 per user) were more persistent and tended to lockup resources more in 5.2 than with ADO and v. 6.x ......we ran into a 300 user limit on version 4.x back in 2000.....DOG SLOW.
RAM, multiple processors, making sure nothing but SQL Server is on one box, SYNC is on ONE box, FTP is on ONE box, EXCHANGE is not involved......
We used to have installations where they had Interbase and everything else on one 2 Gb RAM box with a single 300 Mhz processor......
Ouch.
So yes, performance suffers when you have hundreds of users in SQL Server and SLX 5.2.6.....they do have Multiple connections per SLX Application running against the SQL Server... and we weren't using ADO back then.
|
|
|
|
Re: Multiple SQL COnnections
Posted: 09 Aug 07 2:42 PM
|
We have about 150 Remotes and 200 Network users. The server is a dedicated server as the sync server is on another box. There is plenty of processors (3.00 gigahertz Intel Xeon MP (8 installed)
), memory(32768 Megabytes Installed Memory) and gigabit network cards, so I'm thinking it may be a indexing issue or perhaps a network traffic problem?
The users are reporting difficulty with creating groups and lookups. The application will just hang for a little while and sometiimes it won't come back.
Any ideas on something to try? |
|
|
|
Re: Multiple SQL COnnections
Posted: 09 Aug 07 2:49 PM
|
SLX 5.2.6 and before does NOT use ADO. Multiple connections per SQL Client are established when they log in. We physically reached a limit many times...... your mileage will not vary. That's one reason that SLX introduced v 6. many years ago.
How about CITRIX or Terminal Server.....they only establish one server side connection to SQL..... I know a customer that has been connecting 400 users for years.....they put about 50 users on a CITRIX box....
Is there a router in the way?
it's a SQL Server issue.....(and how SLX is connecting to SQL Server through BDE and the SQL Client Tools......)
|
|
|
|