I am writing this question to clarify for myself whether what I assumed so far is really (still?) true.
Required services of the 'quasi server' would be file services (SMB) and Microsoft SQL Server (ODBC).
The clients would use the services of this 'quasi server' from a Microsoft Access application.
So far I have assumed that this scenario should be strictly avoided, as Windows client operating systems such as 10/11, unlike Windows server operating systems, allow a maximum of 20 simultaneous incoming connections (across the board) and even one Microsoft Access client can already hold several database connections simultaneously, which could lead to unpredictable behaviours.
Now I have read here (https://learn.microsoft.com/en-us/answers/questions/1008380/maximum-number-of-concurrent-connections) and here (https://learn.microsoft.com/en-us/a...ical-limitations-when-using-windows-10-as-the) that you have to differentiate:
and
So it seems that this limit of 20 simultaneous incoming connections applies to file services (SMB), for example, but not to SQL Server services (ODBC).
- Is this really the case? Is there really no limit to the number of simultaneous incoming database connections?
- Or does this possibly depend on whether they are made with TCP/IP / NETBIOS / Named Pipes?
- What is the legal situation? Can does not always mean may...?
What is your opinion/experience on this?
Required services of the 'quasi server' would be file services (SMB) and Microsoft SQL Server (ODBC).
The clients would use the services of this 'quasi server' from a Microsoft Access application.
So far I have assumed that this scenario should be strictly avoided, as Windows client operating systems such as 10/11, unlike Windows server operating systems, allow a maximum of 20 simultaneous incoming connections (across the board) and even one Microsoft Access client can already hold several database connections simultaneously, which could lead to unpredictable behaviours.
Now I have read here (https://learn.microsoft.com/en-us/answers/questions/1008380/maximum-number-of-concurrent-connections) and here (https://learn.microsoft.com/en-us/a...ical-limitations-when-using-windows-10-as-the) that you have to differentiate:
You may allow up to 20 other devices to access the software installed on the licensed device for the purpose of using the following software features: file services, print services, Internet information services, and Internet connection sharing and telephony services on the licensed device. You may allow any number of devices to access the software on the licensed device to synchronize data between devices.
This section does not mean, however, that you have the right to install the software, or use the primary function of the software (other than the features listed in this section), on any of these other devices.
and
The limits on file & printer connections has nothing to do with any other process on the server, including SQL Server.
So it seems that this limit of 20 simultaneous incoming connections applies to file services (SMB), for example, but not to SQL Server services (ODBC).
- Is this really the case? Is there really no limit to the number of simultaneous incoming database connections?
- Or does this possibly depend on whether they are made with TCP/IP / NETBIOS / Named Pipes?
- What is the legal situation? Can does not always mean may...?
What is your opinion/experience on this?
Last edited: