March 9, 2011 at 11:57 am
Hi,
I'm trying to define requisites to a server with windows 2008 server and sql server 2008 to allow 30 user connections at same time to sql server, and mantaining the performance..
Have you guys any advice?
Thanks.
March 9, 2011 at 12:15 pm
You can limit the maximum number of concurrent connections, but it's more usual to use connection pooling or whatever in your data access layer, instead of at the database server.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
March 9, 2011 at 12:42 pm
GSquared,
Thanks for your opinion. 🙂
March 9, 2011 at 5:54 pm
If what you are looking for is the requirements (CPU, memory, Disk I/O, etc.) that are needed to support 30 simultaneous user connections you would need more information about what those connections are doing.
Do you have any stats on the normal work load for each connection? For example: How many queries are run, are they simple/quick queries, or large complicated queries? (I can run a single query that will bring our production server to it's knees for 5 hours, but it can handle 30 simultaneous normal user connections with no problem.)
March 10, 2011 at 4:22 am
Yes, i'm looking for the CPU, memory requirements.
Each user runs the application that could perform 1 more complex query (a search in database in 2, 3 tables with several and optional parameters) and then about 10 more simple succeeding queries.
How do i exactly check if the query is complex/simple?
One detail that i don't know if it is relevant is that the application connects with database using a web service whitch connects to database using always the same database user.
Hope this could help to define my problem..
Regards
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply