Share via

Azure SQL Database Hyperscale Serverless

Fernando Gutierrez 325 Reputation points
2025-12-10T12:50:29.5466667+00:00

I have a database in Azure. It's an SQL Database that runs only one process per day, just one in 24 hours. When this process runs, it consumes a lot of DTUs and CPU, requiring approximately 4 to 6 vcores. Therefore, I configured this database with a Hyperscale Serverless tier, since it's idle the rest of the day. I set the maximum number of vcores to 6 and configured it to have 1 replica.

My question is, how can I verify, or how can I tell, that the process isn't running the rest of the day, and that the tier I've set is the minimum, not the maximum number of vcores, so it's not consuming excessive resources and incurring significant costs?

Thanks

User's image

Azure SQL Database
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pilladi Padma Sai Manisha 500 Reputation points Microsoft External Staff Moderator
    2025-12-10T22:10:06.78+00:00

    Hi Fernando Gutierrez,

    It sounds like you've got a good setup with your Azure SQL Database in the Hyperscale Serverless tier, especially since your process only runs once a day. To ensure you're not incurring unnecessary costs and that the database is indeed idle the rest of the day, here are some steps you can take:

    1. Monitoring CPU and DTU Usage: You can use the Azure portal to monitor the performance metrics of your database. Navigate to your SQL Database, and under the "Monitoring" section, look at "Metrics." Here, you can view metrics such as DTU usage, CPU percentage, and vCore utilization. Check these metrics during the hours that your process is not running to ensure they are low.
    2. Set Up Alerts: You can configure alerts in the Azure portal for when your DTU usage or CPU usage exceeds a certain threshold during the idle times. This will help you to be notified if your database is consuming resources unexpectedly.
    3. Database Audit Logs: Consider enabling auditing on your SQL Database. This will allow you to track all actions performed on the database, helping you to confirm that no background processes are running outside your scheduled task.
    4. Billing Insights: Use the Azure Cost Management tool to get insights into your spending. This way, you can always understand what parts of your database configuration are costing you the most and see if any adjustments can be made.
    5. Resource Limits: Keep in mind that as you’ve set a maximum of 6 vCores, your configuration should only consume more resources during the process's runtime—make sure your minimal vCore setting aligns with your needs outside of this.
    6. Dynamic Scaling: The Hyperscale tier allows for the scale up and down of resources based on workload demands. Ensure that your minimum vCore setting (if you’ve set one) is suitable for your needs.

    By keeping an eye on the usage metrics and setting up alerts, you'll be able to ensure that your database isn't consuming resources unnecessarily outside of your defined process.

    References for Further Reading:

    Hope this helps! If you have any more questions or need further clarification, feel free to ask!

    0 comments

Your answer

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