SQL Server 2008 dynamically adjusts the
number of simultaneous connections to the server if the User Connections
configuration setting is left at its default of 0.
Even if you set this value to
a different number, SQL Server does not actually allocate the full amount of
memory needed for each user connection until a user actually connects. When SQL
Server starts, it allocates an array of pointers with as many entries as the
configured value for User Connections. If you must use this option, do not set
the value too high because each connection takes approximately 28 KB of
overhead regardless of whether the connection is being used.
However, you also
don’t want to set it too low because if you exceed the maximum number of user
connections, you receive an error message and
cannot connect until another connection becomes available. (The
exception is the DAC connection, which can be used.) Keep in mind that the User
Connections value is not the same as the number of users; one user, through one
application, can open multiple connections to SQL Server. Ideally, you should
let SQL Server dynamically adjust the value of the User Connections
option.
http://www.mybasicknowledge.com/2012/09/sql-server-database-options-and.html
http://www.mybasicknowledge.com/2012/09/using-windows-system-monitor-for-sql.html
http://www.mybasicknowledge.com/2012/09/sql-server-database-options-and.html
http://www.mybasicknowledge.com/2012/09/using-windows-system-monitor-for-sql.html