Auto Scale - Azure SQL elastic pools
We have received a few inquiries and service requests regarding having an automatic scale for Azure SQL elastic pools and this blog was written based on the previous great blog article by our colleague Julio Calderón (How-to auto-scale Azure SQL Databases - Microsoft Community Hub) which explained how to perform auto scale for Azure SQL database. This blog article will be a continuation of the previous one to cover the Azure SQL elastic pool.Lesson Learned #441: Monitoring TempDB Transactions Space in Azure SQL Elastic Pools with PowerShell
Today, we addressed a service request from our customer who needed to identify both the session and the text of the query responsible for a significant increase in the transaction log of the tempdb among the databases within the Elastic DB Pool. This increment in the transaction log was leading to an error message: “Msg 9002, Level 17, State 4 - The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION', with the holdup identified as (XXX:NNN:YYY)" The TempDB database in Azure SQL plays a vital role in the performance and management of your SQL instances. Monitoring its transactions closely helps ensure smooth operation and efficient troubleshooting when issues arise. In this article, we’ll explore a PowerShell script designed to monitor transactions within TempDB in the context of Azure SQL Elastic Pools. Additional Information: Azure SQL DB and TEMPDB usage tracking - Microsoft Community Hub
