Concurrency Control

Multi-version Concurrency Control (MVCC)

In a multi-user scenario, the application will be split. This means that the tables are in one file called the back end (typically stored on a shared network folder) and the application components (forms, reports, queries, code, macros, linked tables) are in another file called the front end. The linked tables in the front end point to the back end file. Each user of the Access application would then receive his or her own copy of the front end file.

Logging

Not Supported

Stored Procedures

Not Supported

Checkpoints

Non-Blocking

Foreign Keys

Supported

Indexes

B+Tree

Microsoft Access only support B+ tree index natively.

Query Interface

Custom API

Access has a query interface, forms to display and enter data, and reports for printing.

Data Model

Relational

Access tables support a variety of standard field types, indices, and referential integrity including cascading updates and deletes.

Views

Not Supported

Isolation Levels

Read Uncommitted

Access support multiple isolation levels including Read Uncommitted, Read Committed, Repeatable Read, Snapshot Isolation and Serializable.

Compression

Bit Packing / Mostly Encoding

By default, Microsoft Access uses unicode compression when creating the field via the table properties., all data for the text data types (Text, Memo, or Hyperlink field) are stored in the Unicode 2-byte character format.

Storage Architecture

Disk-oriented

Microsoft Access can scaled to enterprise-level solutions by linking to multiple databases on disk or using a back-end database like Microsoft SQL Server.