Technical Issue

Hi Nitin Jadva - admin,

It looks like you're looking to find a more cost-effective option for your Azure Database for MySQL service. Here are some suggestions to help you reduce your fees:

Select a Different Tier: Azure Database for MySQL offers different service tiers and compute sizes. You might consider switching to a lower-tier plan or a less expensive pricing tier if your workload allows for it. You can find more info on the service tiers here.

Optimize Resource Usage: Assess your current usage—if your database server is consistently under-utilized, consider scaling down the resources (CPU, memory) allocated to it.

Use Azure Reservations: If you plan to use Azure Database for MySQL for a long period, think about purchasing reserved capacity. This can save you money if you're committing to a one-year or three-year usage term.

Utilize Auto Stop and Start: If your usage is intermittent, set up auto-stop and auto-start features for the database, so you only pay for the time it’s running. You can find more details on enabling this feature in the article about auto-stop and start here.

Monitor and Adjust: Utilize Azure’s monitoring tools to keep an eye on performance metrics. This can help you identify if there are inefficiencies causing unnecessary costs.

Consider Flexible Server Options: If you're currently on the Single Server, explore the Flexible Server options which could offer better flexibility for resource scaling and pricing.

Hope this helps you find a more affordable solution for your MySQL database! Let me know if you have any other questions or need further assistance.

References

• Azure Database for MySQL - Flexible Server Overview
• Service Tiers for Azure Database for MySQL
• Auto Stop and Start for Azure Database for MySQL

Hello,

Thanks for raising this question in Azure Q&A forum.

Unfortunately, I was unable to retrieve the URL you mentioned in the question. Could you please provide a screenshot of the issue?

Best Reards,

Jerald Felix

Hello Nitin Jadva - admin,

Thanks for raising this question in Azure Q&A forum

To reduce the costs for your Azure Database for MySQL Flexible Server (ssmb-sydney-db), here are a few practical strategies you can implement:

Scale down Compute Tier: If your workload doesn't require consistent high performance, consider switching to the Burstable (B-series) compute tier. It is significantly cheaper than General Purpose or Memory Optimized tiers.

Stop the Server: If this is a non-production or development server, you can manually stop the server when it is not in use (up to 7 days at a time). You will only be billed for storage while it's stopped.

Storage and Backups: Review your storage size and backup retention period. Reduce the backup retention period to the minimum required (e.g., 7 days) and avoid over-provisioning storage, as it cannot be scaled down later.

Reserved Instances: If this is a production server that runs 24/7, consider purchasing Azure Reserved Instances (RIs) for 1 or 3 years. This can save you up to 65% on compute costs compared to pay-as-you-go pricing.

If helps kindly accept the answer.

Best Regards,

Jerald Felix