Azure MySQL Database Replication for Qlik Sense - Costs saving and alternative

Vijay Ganji 141 Reputation points
2025-04-06T20:17:10.57+00:00

I am trying to configure our Azure MySQL Database flexible server with Qlik Sense. As I understand that using Replication is only to have a database replica which can be used for Qlik Sense configuration instead of direct production database to be configured.

If there is some other way where we can set up a database replica for using in Qlik sense configuration apart from Replication of whole instance of Azure MySQL Database flexible server. We are using General Purpose so it is costing us around ~1400 Euros for year even for replica instance. In total for year it costs us ~3K euros for both production and replica secondary readable instance.

Please advise how to save cost in this case. Any alternatives for setting up Qlik Sense apart from Replication. Thanks

I already did a review of available options that I am aware of and reaching out for help to understand unknown options to save cost.

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
994 questions
{count} votes

Accepted answer
  1. Manasa Akula 680 Reputation points Microsoft External Staff Moderator
    2025-04-09T06:23:42.8333333+00:00

    Hi Vijayakumar Ganji

    As you've mentioned is about how to leverage serverless options for your Qlik Sense data source, given that you're already using MySQL Flexible Server as the main production database for the application. Additionally, you mentioned that you cannot have a standalone serverless database because the application depends on the Flexible Server as its production database.

    For this here is a clearer explanation:

    To take advantage of serverless options while still using MySQL Flexible Server as the production database, with the goal of optimizing costs and scaling infrastructure without disrupting your production environment, you can implement a hybrid architecture. This will involve incorporating serverless features in areas that don't affect your critical transactional workloads but help reduce costs and scale your system as needed.

    Replicate Data to Serverless Databases for Read-Heavy Workloads

    Flexible Server for Production:

    • Your MySQL Flexible Server will remain your primary production database that handles transactional operations, ensuring the stability and performance of your core application.

    Serverless Database for Reporting/Analytics:

    • For workloads that are more read-heavy and do not require real-time data from the production database, you can replicate data to a serverless database. This will allow you to scale based on demand and optimize costs.

    This is How you can Implement:

    Data Replication:

    • Set up replication from your Flexible Server to a serverless database (such as Azure SQL Database Serverless, or a MySQL-compatible serverless option). Use MySQL's native replication or managed services (like Azure Database Migration Service) to sync data from your production environment to the serverless database. HELPS:
    • Your production MySQL Flexible Server remains isolated, while the serverless database handles the read-heavy, analytical, or reporting queries. The serverless database scales based on the amount of compute required for queries, ensuring cost efficiency during periods of low demand.
    • Use Qlik Sense with Serverless Database: Connect Qlik Sense to the serverless database to run analytical queries and generate reports. This avoids overloading the production MySQL Flexible Server with reporting queries while providing the flexibility to scale during peak reporting times.

    Benefits:

    • Cost Optimization: You pay only for the compute resources used by the serverless database, helping you reduce costs during periods of low demand.
    • Scalability: The serverless database can automatically scale resources based on demand, ensuring it can handle heavy reporting or query workloads when needed without having to provision fixed resources.
    • Optimize costs by scaling resources only when needed (e.g., using serverless databases that scale automatically).
    • Ensure stability and performance for your production database by isolating it from read-heavy or heavy computation tasks.
    • Scale infrastructure efficiently with serverless features without the need to provision dedicated servers for each workload.
    • This strategy balances the flexibility and cost benefits of serverless computing with the stability and control of your Flexible Server for critical production data.

    I hope this information helps you find a more cost-effective solution for your Qlik Sense setup use serverless option for flexible server. Please do let us know if you have any further queries.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.