But, tuning an application can minimize resource requirements and lower monthly bills when you use the service tiers in Azure SQL Database and Azure SQL Managed Instance. This approach might be a good idea if you don't want to change a key application during a busy period. Some customers might choose not to tune an application, and instead choose to over-provision hardware resources. With the model of paying for capacity on demand, you can tune your application to use the minimum resources needed now, instead of over-provisioning on hardware based on guesses of future growth plans for an application, which often are incorrect.
When you use Azure SQL, it's a good idea to interweave the process of running an application and tuning it. Hardware and product licenses are purchased first, and performance tuning is done afterward. In traditional on-premises SQL Server, the process of initial capacity planning often is separated from the process of running an application in production. Additionally, this article assumes that you do not have a CPU resources, running-related performance issue that can be resolved by increasing the compute size or service tier to provide more resources to your database. It also assumes that you have reviewed An overview of monitoring and tuning and its related articles related to troubleshooting performance issues. This article assumes that you have already worked through the Azure SQL Database database advisor recommendations and the Azure SQL Database auto-tuning recommendations, if applicable. Tune the database by changing indexes and queries to more efficiently work with data.Tune your application and apply some best practices that can improve performance.Once you have identified a performance issue that you are facing with Azure SQL Database and Azure SQL Managed Instance, this article is designed to help you: