Post reply

Maximum connections.

  • April 18, 2012 at 8:17 am

    #392055

    Hello,

    Somewhere I read that SQL Server 2005 can handle 32,767 user connection at a time.

    Can anyone explain what exactly that means ? What happens if more users try to connect?

    For example, Railway ticket booking system. There will be millions of people trying to to book their tickets.

    How SQL SErver handles this ?

    Thanks in advance.

    Smith.

  • April 18, 2012 at 9:27 am

    #1475415

    It means there can be 32,767 user connections at any given time. This is not to say that millions of people could not use the same database server within the same period of time, just not all at the same exact time. Connection pooling at the application layer enables multiple people to share the same connection as not all people will need to retrieve or store data to the database server at the same exact time.

    I have supported database instances supporting applications with tens of thousands concurrent users where the number of database user connections was in the hundreds, due to the connection pooling happening in the application layer.

    I have only heard of instances where the 32,767 user connection limit was reached due to misbehaving applications, i.e. never heard of a legitimate scenario where 32,767 was a limiting factor for scaling an application or database.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • April 19, 2012 at 11:48 pm

    #1476424

    Thank you so much. More clear now.

    Just one thing, Can I test the 'same' connection shared by multiple users on my local PC ? How to test it ?

    Thanks,

    Smith.

  • April 20, 2012 at 6:32 am

    #1476577

    You would need to write an application wherein you can establish a connection and use it for several processes. I did a quick Google search on "introduction to connection pooling" and came up with the following. Seems like a fairly good overview.

    http://aspalliance.com/1099_Understanding_Connection_Pooling_in_NET.all

    Hope this helps.

    David

    @SQLTentmaker

    “He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply