This post has been republished via RSS; it originally appeared at: New blog articles in Microsoft Tech Community.
We used to have cases where our customers reported a performance issue that is causing delay in their business. Working on this issue we saw that the LOG_RATE_GOVERNOR was the most wait time. In this video below we going to provide us some insights about it,.
Why this issue happened?
- Transaction log rate governance
- Limit high ingestion rates for workloads
- Depends on Service/Database Tier.
- More Information: Resource management in Azure SQL Database - Azure SQL Database | Microsoft Docs
How?
- Azure Portal
- Select * from sys.dm_db_resource_stats
- Select * from sys.dm_exec_requests in combinations with other DMVs.
Best Practices
- Use Business Critical, Premium or Hyperscale if possible.
- Use smaller batches.
- Review if all indexes are needed
- Avoid huge amount like text.
- Implement a more robust retry logic execution.
- Move Historical data to another DB.