Post reply

Maximum Concurrent User Connections

  • October 21, 2003 at 7:47 pm

    #106890

    I'm hoping someone can help me.

    I was wondering if there is any potential performance issues with having the user connections value set to 0 (unlimited)

    Or should you set a maximum number of connections. eg 500

    Thanks

  • October 23, 2003 at 12:50 pm

    #479355

    I think it mostly depends on your hardware and user base.

    From BOL regarding the connections option:

    "Important If you must use this option, do not set the value too high because each connection takes approximately 40 kilobytes (KB) of overhead regardless of whether the connection is being used. If you exceed the maximum number of user connections, you receive an error message and are not able to connect until another connection becomes available."

    My philosophy especially with SQL2K is to let the server manage anything that it can dynamically unless there is a good reason to do otherwise. Setting a static number of connections means that you will always be dedicating a certain amount of overhead that can only be used for this resource and you may wind up shooting yourself in the foot. On the other hand, if your setting is too low it won't accept new user connections. Let SQL Server do the work.

    My hovercraft is full of eels.

  • October 23, 2003 at 6:05 pm

    #479389

    Thanks!!!

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

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