Відео

Hi @cloudway908, you can follow the steps mentioned here to monitor the IOPS utilised: learn.microsoft.com/azure/mysql/flexible-server/concepts-storage-iops#monitor-storage-performance

The ability to use exported backups to spin up a new flexible server is not supported in public preview, but the functionality will become available after the feature goes GA. In the interim, please consider using “on-demand backup” (learn.microsoft.com/azure/mysql/flexible-server/how-to-trigger-on-demand-backup) to restore to a new instance of Azure Database for MySQL - Flexible Server.

We're truly sorry to hear about the challenges you've faced. At Microsoft, we're constantly striving to improve our products and services, and your feedback is invaluable in this process. Regarding the issue with upgrading Azure MySQL from version 5.7 to 8.0, it's designed to be a seamless process that doesn't require software installation. We're concerned to learn about the difficulties you've encountered, especially with Chinese characters. To better understand and resolve the specific issues you're facing, could you please share more details with us via email at <AskAzureDBforMySQL@service.microsoft.com>? Your insights will be directly forwarded to our technical team for a deeper analysis.

Hi @yudhveersingh655 - Yes. You'll need to purchase Power Apps Premium license to use the connectors. For more details, see powerapps.microsoft.com/pricing/ .

No credit card is required to subscribe to our channel.

It's a feature in development that will improve the performance of servers based on the Business Critical SKU.

Hi Ashutosh, for migrating from Azure Database for PostgreSQL - Single Server to Flexible Server, I'd recommend you to refer to this document instead: learn.microsoft.com/azure/postgresql/migrate/concepts-single-to-flexible

Do we need to create target flexible server if yes how?

Hi Sreenivasa, 1) Universal Cross Region Read Replica, i.e., the ability to provision a read replica in another non-paired region is currently in Private Preview, and will be generally available by end of August. If you wish to enrol in Private Preview and test the feature out immediately, please write to AskAzureDBforMySQL@service.microsoft.com. 2) Once you promote a read replica to primary, replication is stopped and the replica becomes a standalone server. If you wish to revert back to primary region, you can create a new replica in primary region and promote it back to primary. However, if you wish to use the same primary server as before, you may need to use Data-in replication (learn.microsoft.com/azure/mysql/flexible-server/concepts-data-in-replication) to synchronize data from the replica (which is now a standalone server) to the primary server, and then cut-over to the primary server.

Hi @chunhingyap, Moving from one subscription to other, but in the same tenant: Click 'move' next to subscription in overview page. - learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resources-overview Moving from one region to other: This is possible using geo-backup restore (Currently you can only do so to a paired region. Support for restoring to any region, i.e. universal restore feature is coming soon!). You can also use paired region read replica to achieve the same with minimal downtime. - learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-move-regions . Moving from one subscription to another or across regions, but to a different tenant: You can use Azure DMS to migrate. - learn.microsoft.com/en-us/azure/dms/

@@AzureDBMySQL unfortunately, it is different tenant.

Hi Ahmed. Can you provide any additional context? Thanks in advance!

The MySQL extension only appears if you are using the Azure Data Studio insiders build (the link is in the description).