azureazure-sql-databaseazure-elasticpool

Is Azure SQL Elastic Pool the Right Choice for Having Separate SQl DB in DEV and PROD Environment


When hosting a Web app using a SQL DB in Azure, we need a separate SQL DB in DEV & PROD environments. Will using Elastic Pool be the better choice than Single database with 1 instance?

It looks like the cost for 2 databases using Elastic Pool (1 for DEV & 1 for PROD) will be the same as the cost for Single database with 1 instance. Does using Elastic Pool add more complexisty for Web App development?


Solution

  • Does using Elastic Pool add more complexity for Web App development?

    No, Elastic Pool doesn't add complexity infect it allows you to easily manage multiple databases which share same configuration and requires unpredictable usage demand.

    Will using Elastic Pool be the better choice than Single database with 1 instance?

    This completely depends on your application requirement. Thought, I don't believe that your DEV environment DB required elastic pool because it's purpose only for Development which doesn't require scalability.

    For PROD environment, Elastic Pool is a good option if your application has below use-cases. Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands.

    enter image description here

    Refer: Elastic pools help you manage and scale multiple databases in Azure SQL Database