A badly designed schema can make a database slow and difficult to query. In this episode of the Azure Database for MySQL - Troubleshooting Series (https://aka.ms/mysql-troubleshooting-..., we walk you through the guiding principles for ensuring that the schemas are designed optimally and provide the best performance for your applications.
0:00 Introduction and episode overview
01:31 Effects of a bad schema design
03:13 Indexes
06:19 Data type considerations
08:06 Primary key design
12:51 Covering index
14:41 Links to resources
Upcoming episode: Checklist for troubleshooting database performance (By Sai Kondapalli)
Resources:
Microsoft Learn documentation - https://learn.microsoft.com/azure/mys...
Get started for free with an Azure free account! - https://aka.ms/try-mysql-free
Follow Azure Database for MySQL on:
• YouTube - / @azuredbmysql
• Twitter - / azuredbmysql
• LinkedIn - https://aka.ms/azuremysql-li
Email us at [email protected].
Series Overview:
The Azure Database for MySQL - Troubleshooting Video Series ( https://aka.ms/mysql-troubleshooting-..., with new episodes released every couple of weeks, provides troubleshooting tips and tricks for potential problem areas, such as low performance, connectivity issues, replication latency, and database corruption.
#AzureDBforMySQL #FlexibleServer #MySQL #Performance