How many users can open a connection to Microsoft Access?

Question

how many users can simultaneously open a connection to a Microsoft Access database? I am using asp.net 4.0 to write my application.

<add name="E_ShopAccessConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=|DataDirectory|\report.mdb;Persist Security Info=True" providerName="System.Data.OleDb"/> 

Answer 1

The Access database has a limit of 256 connections, but in the database drivers there is a limit of 64 connections to the process, and since IIS is one process, your limit is 64.

If you carefully close your connections, commands, and data readers, this is usually enough for a large number of users. Each visitor does not need their own connection.

You will probably encounter other restrictions before your connection ends. If you have a lot of visitors, you will find that the Access database is simply not fast enough and you need a more advanced database system.

If you run out of connections, this is most likely due to the fact that you are not closing the database objects properly, so that they still maintain the connection to the database until the garbage is collected.

Answer 2

According to Microsoft: a maximum of 64 connections per process with a limit of 256 simultaneous open read / write connections to the database .

But with my experience above 20 connections, performance is significantly reduced.

Answer 3

If you use MS Access from ASP.NET, the site operates in the context of a single user, so there should not be too many problems.

[Most people disagree, but I had experience using MS Access with ASP and ASP.NET on a fairly high transactional site, and it worked fine, make sure the database is the latest version of MS access]

I would prefer to use SQL Server Express as an alternative.

Answer 4

Not enough.

Depending on the version, you can have from 5 to 10, but it’s really safe <3 for "high volume per user".

Technically, this could get much higher, but he had a bad impression trying to recover files. Usually we recommend> 5, as the middle one should move to something like SQL Server as a backend with an MS Access mapping for the interface.