You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following sections describe capacity, storage engine support, privilege support, data manipulation statement support, and functional limits in the database service.
12
12
13
-
## Maximum connections
14
-
The maximum number of connections per pricing tier and vCores are as follows:
The minimum and maximum values of several popular server parameters are determined by the pricing tier and vCores. Refer to the below tables for limits.
When connections exceed the limit, you may receive the following error:
33
36
> ERROR 1040 (08004): Too many connections
@@ -37,6 +40,108 @@ When connections exceed the limit, you may receive the following error:
37
40
38
41
Creating new client connections to MariaDB takes time and once established, these connections occupy database resources, even when idle. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that decreases idle connections and reuses existing connections will help avoid this. To learn about setting up ProxySQL, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/load-balance-read-replicas-using-proxysql-in-azure-database-for/ba-p/880042).
39
42
43
+
## query_cache_size
44
+
45
+
The query cache is turned off by default. To enable the query cache, configure the `query_cache_type` parameter.
46
+
47
+
Review the [MariaDB documentation](https://mariadb.com/kb/en/server-system-variables/#query_cache_size) to learn more about this parameter.
@@ -92,5 +197,5 @@ Requires super privileges to create and is restricted. If importing data using a
92
197
- MariaDB server instance displays the incorrect server version after connection is established. To get the correct server instance engine version, use the `select version();` command.
93
198
94
199
## Next steps
95
-
-[What’s available in each service tier](concepts-pricing-tiers.md)
200
+
-[What's available in each service tier](concepts-pricing-tiers.md)
The following sections describe capacity, storage engine support, privilege support, data manipulation statement support, and functional limits in the database service. Also see [general limitations](https://dev.mysql.com/doc/mysql-reslimits-excerpt/5.6/en/limits.html) applicable to the MySQL database engine.
12
12
13
-
## Maximum connections
14
-
The maximum number of connections per pricing tier and vCores are as follows:
The minimum and maximum values of several popular server parameters are determined by the pricing tier and vCores. Refer to the below tables for limits.
When connections exceed the limit, you may receive the following error:
33
36
> ERROR 1040 (08004): Too many connections
@@ -37,6 +40,111 @@ When connections exceed the limit, you may receive the following error:
37
40
38
41
Creating new client connections to MySQL takes time and once established, these connections occupy database resources, even when idle. Most applications request many short-lived connections, which compounds this situation. The result is fewer resources available for your actual workload leading to decreased performance. A connection pooler that decreases idle connections and reuses existing connections will help avoid this. To learn about setting up ProxySQL, visit our [blog post](https://techcommunity.microsoft.com/t5/azure-database-for-mysql/load-balance-read-replicas-using-proxysql-in-azure-database-for/ba-p/880042).
39
42
43
+
## query_cache_size
44
+
45
+
The query cache is turned off by default. To enable the query cache, configure the `query_cache_type` parameter.
46
+
47
+
Review the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_query_cache_size) to learn more about this parameter.
48
+
49
+
> [!NOTE]
50
+
> The query cache is deprecated as of MySQL 5.7.20 and has been removed in MySQL 8.0
Review the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_sort_buffer_size) to learn more about this parameter.
Review the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_join_buffer_size) to learn more about this parameter.
Review the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_max_heap_table_size) to learn more about this parameter.
Review the [MySQL documentation](https://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_tmp_table_size) to learn more about this parameter.
@@ -90,5 +198,5 @@ Requires super privileges to create and is restricted. If importing data using a
90
198
- MySQL server instance displays the wrong server version after connection is established. To get the correct server instance engine version, use the `select version();` command.
91
199
92
200
## Next steps
93
-
-[What’s available in each service tier](concepts-pricing-tiers.md)
201
+
-[What's available in each service tier](concepts-pricing-tiers.md)
94
202
-[Supported MySQL database versions](concepts-supported-versions.md)
0 commit comments