Compare Azure MySQL vs PostgreSQL Limitations & Restrictions

In this post, we compare Azure MySQL vs PostgreSQL limitations and various restrictions that must be considered before deployment.

Table of Contents

Compare Azure MySQL vs PostgreSQL Limitations & Restrictions

This table provides a side-by-side comparison of the limitations of both databases, making it easier to understand the similarities and differences between them.

Feature/Limitation	Azure Database for MySQL	Azure Database for PostgreSQL
Maximum Connections (User)
Basic (1 vCore)	50	50
Basic (2 vCores)	100	100
General Purpose (2 vCores)	145	145
General Purpose (4 vCores)	245	245
General Purpose (8 vCores)	475	475
General Purpose (16 vCores)	945	945
General Purpose (32 vCores)	1495	1495
General Purpose (64 vCores)	1895	1895
Memory Optimized (2 vCores)	295	295
Memory Optimized (4 vCores)	495	495
Memory Optimized (8 vCores)	955	955
Memory Optimized (16 vCores)	1895	1895
Memory Optimized (32 vCores)	1982	1982
Functional Limitations
Dynamic Scaling (Basic Tier)	Not Supported	Not Supported
Decrease Storage Size	Not Supported	Not Supported
Automated Server Version Upgrades	Not Supported	Not Supported
VNet Service Endpoints	General Purpose & Memory Optimized	General Purpose & Memory Optimized
Restoring Deleted Server	Not Supported	Not Supported
UTF-8 Characters on Windows	Partial Support	Partial Support
GSS Error (JDBC versions)	42.2.15 & 42.2.16	42.2.15 & 42.2.16
Storage Size Reduction	Not Supported	Not Supported

Azure MySQL vs PostgreSQL Limitations:

Maximum Connections:
- Basic (1 vCore): 50 user connections
- Basic (2 vCores): 100 user connections
- General Purpose (2 vCores): 145 user connections
- General Purpose (4 vCores): 245 user connections
- General Purpose (8 vCores): 475 user connections
- General Purpose (16 vCores): 945 user connections
- General Purpose (32 vCores): 1495 user connections
- General Purpose (64 vCores): 1895 user connections
- Memory Optimized (2 vCores): 295 user connections
- Memory Optimized (4 vCores): 495 user connections
- Memory Optimized (8 vCores): 955 user connections
- Memory Optimized (16 vCores): 1895 user connections
- Memory Optimized (32 vCores): 1982 user connections
Functional Limitations:
- Dynamic scaling to and from the Basic pricing tiers is not supported.
- Decreasing server storage size is not supported.
- Server version upgrades: Automated migration between major database engine versions is not supported.
- VNet service endpoints: Support is only for General Purpose and Memory Optimized servers.
- Restoring a server: Restoring a deleted server is not supported.
- UTF-8 characters on Windows: In some scenarios, UTF-8 characters are not fully supported.
- GSS error: Known to affect JDBC driver versions 42.2.15 and 42.2.16.
- Storage size reduction: Storage size cannot be reduced.

Azure Database for PostgreSQL – Limitations

Maximum Connections:
- Basic (1 vCore): 50 user connections
- Basic (2 vCores): 100 user connections
- General Purpose (2 vCores): 145 user connections
- General Purpose (4 vCores): 245 user connections
- General Purpose (8 vCores): 475 user connections
- General Purpose (16 vCores): 945 user connections
- General Purpose (32 vCores): 1495 user connections
- General Purpose (64 vCores): 1895 user connections
- Memory Optimized (2 vCores): 295 user connections
- Memory Optimized (4 vCores): 495 user connections
- Memory Optimized (8 vCores): 955 user connections
- Memory Optimized (16 vCores): 1895 user connections
- Memory Optimized (32 vCores): 1982 user connections
Functional Limitations:
- Dynamic scaling to and from the Basic pricing tiers is not supported.
- Decreasing server storage size is not supported.
- Server version upgrades: Automated migration between major database engine versions is not supported.
- VNet service endpoints: Support is only for General Purpose and Memory Optimized servers.
- Restoring a server: Restoring a deleted server is not supported.
- UTF-8 characters on Windows: In some scenarios, UTF-8 characters are not fully supported.
- GSS error: Known to affect JDBC driver versions 42.2.15 and 42.2.16.
- Storage size reduction: Storage size cannot be reduced.

Comparison: Upon reviewing the limitations of both Azure Database for MySQL and Azure Database for PostgreSQL, it’s evident that they share many similarities regarding connection limits and functional limitations. Both databases have the same connection limits based on their pricing tiers and vCores.

Their functional limitations, such as dynamic scaling restrictions, server version upgrade constraints, and storage size reduction limitations, are also identical.

However, users should be aware of specific nuances and details related to each database system and consider their individual requirements when choosing between the two.

Conclusion:

Both Azure Database for MySQL and Azure Database for PostgreSQL exhibit striking similarities in their limitations, especially concerning connection limits and functional constraints.

Their identical restrictions across various pricing tiers and vCores highlight Azure’s consistent infrastructure and design principles. However, potential users should be cognizant of these limitations when making a choice, ensuring that their specific requirements align with the capabilities of the chosen database system.

Disclaimer: The Questions and Answers provided on https://www.gigxp.com are for general information purposes only. We make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose.