Generally, you are advised not to play with the “Maximum number of concurrent connections” setting in SQL Server, especially if you are not exactly sure of what you are doing. The key word in the previous sentence is “simultaneous”.Īs this relevant super cool Microsoft Docs article says, “the actual number of user connections allowed also depends on the version of SQL Server that you are using, and also the limits of your application or applications and hardware…”įor example, SQL Server 2017, allows a maximum of 32,767 user connections. The “Maximum number of concurrent connections” setting in SQL Server specifies the maximum number of simultaneous user connections on a SQL Server instance.
The theory behind the Maximum Number of Concurrent Connections setting in SQL Server To help to overcome an unpleasant situation where this setting might have been changed and you locked out yourself from accessing your SQL Server instance.To present the theory behind the “Maximum number of concurrent connections” setting,.In case you changed this setting there is the risk to lock yourself out of your SQL Server instance because there is the possibility that other connections (if we are talking about an active database environment with client connections) might take over the available connection slots, thus keeping you out of the SQL Server instance.
This setting by default is set to 0 (zero), which means “unlimited” concurrent connections and it is generally advised not to change it.
Among its plethora of available and useful settings, SQL Server has a setting that is called “ Maximum number of concurrent connections“.
0 kommentar(er)
