Each Access Services application in Microsoft 365 and SharePoint Online creates a corresponding SQL database that is subject to resource consumption limits. These limits are per database and apply whether using the web user interface or direct ODBC connection.
|
Important Access Services 2010 and Access Services 2013 are being removed from the next release of SharePoint. We recommend you do not create new web apps, and migrate your existing apps to an alternative platform, such as Microsoft Power Apps. You can share Access data with Dataverse, which is a cloud database upon which you can build Power Platform apps, Automate workflows, Virtual Agents, and more for the web, phone, or tablet. For more information, see Get started: Migrate Access data to Dataverse. |
Access web app limits
|
Limit |
Maximum value |
Notes |
|---|---|---|
|
Maximum query performance level |
5 DTUs |
This limit is calculated as a number of Database Transaction Units or DTUs, which is a blended measure of CPU, memory, and I/O (data and transaction log I/O). If your query exceeds the resource consumption limits, you'll receive SQL error 10928. |
|
Maximum Access app database storage size |
1 GB |
1 GB is the limit for the database storage. If the app exceeds the size limit, you'll receive SQL error 40544. |
How to avoid being throttled
If queries are being throttled, there may be some ways that you can reduce the amount of resources consumed without reducing the amount of data that your Access web app is accessing. Here are some general tips to reduce resource consumption:
-
Identify the top queries that can potentially be tuned for improved performance.
-
Transfer non-OLTP processing to a local Access database (.ACCDB) or an Azure SQL database.
