'Too many connections' is an issue that could affect 32-bit SQL Server, but is far less likely to affect 64-bit SQL Server.
With 32-bit, SQL Server has to fit a great deal into memory below the 4GB line. If you have maxed out on AWE memory, SQL has to fit everything bar the buffer pool in about 1.7 GB. If enough people try to connect, SQL will eventually reject connections because it cannot fit everything within that 1.7 GB. Adding extra memory will not help, because this does not add anything extra to the memory below the 4GB line.
In 64-bit SQL Server, any of SQL Server's memory pools can exist anywhere in memory. It is still true that if you have enough connections you may restrict the memory that SQL Server can use for other purposes, but the bar is far higher on 64-bit. You can also easily mitigate the problem by adding extra memory to the box, providing you have spaer memory slots.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara