Max log size and max tempdb size are documented for the vCore-based model, please document these limits for the DTU-based model as well
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@iizotov Thanks for the valuable feedback. I have assigned this issue to the content author to help you further.
@CarlRabeler could you please help here in enhancing the document.
Documenting at what point LOG IO gets throttled for each service level would be very helpful. Does it vary only between tiers (Standard vs. Premium, for example) or at various levels within each tier (P1 vs. P2, for example)?
@m60freeman researching...
Done - live later today into blob storage - https://github.com/MicrosoftDocs/azure-docs-pr/pull/68453
@angoyal-msft @Mike-Ubezzi-MSFT please close
We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.
This change has not appeared in the publicly visible page. I see it on https://docs.microsoft.com/en-us/azure/sql-database/sql-database-vcore-resource-limits-single-databases, but not on https://docs.microsoft.com/en-us/azure/sql-database/sql-database-dtu-resource-limits-single-databases.
@Mike-Ubezzi-MSFT This change has not appeared in the publicly visible page. I see it on https://docs.microsoft.com/en-us/azure/sql-database/sql-database-vcore-resource-limits-single-databases, but not on https://docs.microsoft.com/en-us/azure/sql-database/sql-database-dtu-resource-limits-single-databases. It needs to be added to the latter.
@CarlRabeler Can you confirm that max log size and max tempdb size are items that should be/should not be listed in the DTU-based document: Resource limits for single databases using the DTU-based purchasing model? This issue was filed specifically for the DTU-based document but the vCore-based document was updated via the referenced pull request?!
The vCore-based document was updated: Azure SQL Database vCore-based purchasing model limits for a single database
@m60freeman @iizotov The nature of DTU-based purchasing model (per Azure SQL Database purchasing models is a basic pre-configured deployment, as these items could be managed by the service and not necessarily static limits.
DTU-based model
This model is based on a bundled measure of compute, storage, and IO resources. Compute sizes are expressed in terms of Database Transaction Units (DTUs) for single databases and elastic Database Transaction Units (eDTUs) for elastic pools. For more on DTUs and eDTUs, see What are DTUs and eDTUs?.
Best for customers who want simple, pre-configured resource options.
vCore-based model
This model allows you to independently choose compute and storage resources. The vCore-based purchasing model also allows you to use Azure Hybrid Benefit for SQL Server to gain cost savings.
Best for customers who value flexibility, control, and transparency.
@Mike-Ubezzi-MSFT @m60freeman Tempdb limits for DTU purchasing model are published here: https://docs.microsoft.com/en-us/sql/relational-databases/databases/tempdb-database?view=sql-server-2017#tempdb-database-in-sql-database - will add link. Max log size is not a currently documented value.
Documenting at what point LOG IO gets throttled for each service level would be very helpful. Does it vary only between tiers (Standard vs. Premium, for example) or at various levels within each tier (P1 vs. P2, for example)?
I still see nothing that addresses this issue with regard to the DTU model other than "these items could be managed by the service and not necessarily static limits", which doesn't really tell me anything. Isn't there any more information available and that could be added to this page?
Documentation as it stands on this subject is here:
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-resource-limits-database-server#transaction-log-rate-governance
And resources by tier here:
vCore Model: Azure SQL Database vCore-based purchasing model limits for a single database
DTU Model: Resource limits for single databases using the DTU-based purchasing model