Understanding Performance in Basic Tier for Azure Database PostgreSQL and MySQL

Azure Database for PostgreSQL and MySQL have similar architectures for performance tiers. While Microsoft recommends to choose between the General Purpose and the Memory Optimized versions, some users might consider Basic Tier servers as they believe their workload is not that aggressive against resource utilization. Basic Tier servers were built for testing, development or small-scale…


Azure Database for MySQL server has gone away

One of the common MySQL server errors is “MySQL server has gone away”. This is a pretty generic error and can happen because of a server error or a client-side error. While Azure has automated bots which are used to detect and address server side issues, this tutorial will discuss client-side issues that can cause…


How to Scale up Azure Database for MySQL from Basic Tier to General Purpose Tier

Scaling up from Basic Tier to General Purpose or Memory Optimized servers is not supported and the only way to achieve this is by exporting your databases from your Basic Tier server and restore the databases at a newly created server in the desired service Tier. You can use mysqldump to backup your databases and…


Azure SQL DB with more than 4 readable secondaries

If you try to create more than 4 geo-replicas in the Portal it will fail with the error message “Replication limit reached. The database ‘XXXXX’ cannot have more than 4 replication relationships.” There are 3 ways to resolve this problem:


Azure Database for PostgreSQL performance Quick Tips

To make sure that you are running your Azure Database for PostgreSQL at its best capabilities, please review the following recommendations and best practices. 1. Server Resource Utilization Make sure that your Azure Database for PostgreSQL instance does not run under a high utilization which can cause query execution latencies. Please visit the Azure Portal…


Unable to view LTR Backups for Azure SQL Database servers

Consider that you have configured the LTR Backup for your Azure SQL Database and you are not able to view it on the Portal. Figure 1: LTR configure policies pane   And when you click on available backups you do not see the list of backups. Figure 2: Available Backups pane This might be related…


Change collation of existing Azure SQL database

When you are creating a new database you can change the collation in the portal Or else using TSQL (https://docs.microsoft.com/en-us/sql/relational-databases/collations/set-or-change-the-database-collation?view=azuresqldb-current)   However there is no easy way at this moment to change an existing database collation. The workaround is to use the BACPAC that can be used like the sample below


Long Retention policies configuration are not saved

If you go to servers and select  database name  it will be opened a window to allow you configure LTR policies, but then these options are not saved. Reproduction steps: 1.- Go to servers – Manage Backups – Configure policies and press on database name 2.- You set 3 weeks to keep, of any other…


Understanding Dynamic Data Masking in Azure SQL DB

Understanding Dynamic Data Masking. When dynamic data masking is applied, the main objective is to limit the exposure of confidential information to users who do not have the necessary privileges to observe confidential information. Problem Summary. Once the masking is done in a column that shares tables and different queries are made using the UNION…