Recent

Author Topic: Split Database for multi-user access without server  (Read 401 times)

lawman

  • New Member
  • *
  • Posts: 42
Split Database for multi-user access without server
« on: October 16, 2020, 11:37:45 pm »
ms-access has a facility to split its jet2 database into frontend and backend.

The backend stores the data in a file on a shared network drive.

The frontend stores the queries/forms in a file on the client user machine.

Using this 'split' technique, multiple users approx 200 can use concurrently use the database without any problems.

In essence, ms-access is allowing a serverless multi-user database for 200 users on a network shared drive without any problems.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other-mso_o365b/ms-access-multiple-users-working-in-one-database/68a1d292-5b19-421f-b730-17b98be50103


My queries are:

1.   As lazarus can also connect to a jet2 database, is this split functionality available using lazarus for multi-user serverless read/write usage?

2.   If ms-access can manage to use a serverless file on a network share for 200 users to read/write concurrently, why can't other serverless systems such as sqlite/firebird do something similar?

3.  Does anyone understand the logic of how it manages 200 users to read/write a single database file on a network share without problems?

Thanks
 

Dan3468298

  • Full Member
  • ***
  • Posts: 129
Re: Split Database for multi-user access without server
« Reply #1 on: October 22, 2020, 02:25:38 pm »
You will not be able to support 200 users on JET.   IIRC a max of 20 users depending on use case is recommended.
MacOS 10.15.5/Lazarus 2.0.10 Build 2020-07-07

valdir.marcos

  • Hero Member
  • *****
  • Posts: 1007
Re: Split Database for multi-user access without server
« Reply #2 on: October 22, 2020, 06:57:00 pm »
ms-access has a facility to split its jet2 database into frontend and backend.

The backend stores the data in a file on a shared network drive.

The frontend stores the queries/forms in a file on the client user machine.

Using this 'split' technique, multiple users approx 200 can use concurrently use the database without any problems.

In essence, ms-access is allowing a serverless multi-user database for 200 users on a network shared drive without any problems.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_other-mso_o365b/ms-access-multiple-users-working-in-one-database/68a1d292-5b19-421f-b730-17b98be50103


My queries are:

1.   As lazarus can also connect to a jet2 database, is this split functionality available using lazarus for multi-user serverless read/write usage?
If you want a serverless solution, why don't you use xBase?
https://en.wikipedia.org/wiki/XBase
https://wiki.freepascal.org/Lazarus_Tdbf_Tutorial

Quote
2.   If ms-access can manage to use a serverless file on a network share for 200 users to read/write concurrently,
It's hard to believe that MS Access would be able to handle 200 simultaneous connections without problems. I've never seen that.

Quote
why can't other serverless systems such as sqlite/firebird do something similar?
SQLite is not designed for multi-user environment.
Firebird can be embbeded for a single connection such as SQLite, but it's not serverless at all.

Quote
3.  Does anyone understand the logic of how it manages 200 users to read/write a single database file on a network share without problems?
Using a single database file shared on a network drive is a bad idea nowadays.
xBase worked like that, try xBase.
Or do yourself a favor and use a real server solution like Firebird, Postgresql, MariaDB etc.

Quote
Thanks

 

TinyPortal © 2005-2018