Closed Zingonead closed 4 years ago
@Zingonead Thank you very much for the detailed feedback. Was there a specific document you were sourcing to initiate this feedback? Because the issue was created without being associated with a specific document, I took the liberty of choosing the best possible doc to file this issue under. If there is another document that you feel needs this verbiage added, please comment with the specific link. In general terms, Azure SQL Database is a nameplate for several specific services: Azure SQL Database - Singleton, Azure SQL Database - Managed Pools, and Azure SQL Database - Serverless. There are nuances between each but the core SQL engine process is the same. Azure SQL Managed Instance is an example of a unique service and has its own set of documents.
Good morning Mike, The related documentation is https://docs.microsoft.com/en-us/azure/sql-database/sql-database-features As per the below screenshot, Azure SQL DB, the “Hyperscale tier” is not mentioned in the list of Column Store indexes compatibility: [cid:image003.png@01D546CF.31A15950]
Hyperscale is a different pricing tier like “General Purpose tier” and “Business Critical” as below: [cid:image007.png@01D546CF.31A15950] I created an Azure SQL Hyperscale, created a column store index and it is included as per the below screenshot [cid:image008.png@01D546CF.31A15950] Ask : Could you please update the documentation to include Hyperscale in the list?
Best regards, Adriano
Good morning Mike,
The documentation concerned is "https://docs.microsoft.com/en-us/azure/sql-database/sql-database-features".
In the latter link the “Hyperscale tier” is not mentioned in the list of Column Store indexes compatibility.
Hyperscale is a different vCores pricing tier like “General Purpose tier” and “Business Critical”.
I created an Azure SQL Hyperscale 2vCores, created table with a column store index and it works as confirmed in another link "https://docs.microsoft.com/en-us/azure/sql-database/sql-database-vcore-resource-limits-single-databases#hyperscale-service-tier".
Ask : Could you please update the documentation available at "https://docs.microsoft.com/en-us/azure/sql-database/sql-database-features" to include the "Hyperscale tier" in the list of Column Store indexes compatibility?
Best regards, Adriano
@jovanpop-msft With Hyper-scale
being a new deployment option, the ask is that it is detailed as part of Single Database and Elastic Pools or becomes a 3rd column to differentiate it amongst the available deployment options. This is potentially not a small edit, so bringing this to the attention of the PG and doc teams @CarlRabeler. Please let me know if there is a direction you would like to take and I can do the pull request.
@stevestein for awareness and discussion
Change is merged in #91425 (private branch). Generally information about HyperScale are centralized on single page. @stevestein please contact @denzilribeiro regarding the plans for updating rest of documentation.
@stevestein and @denzilribeiro Please check this issue.
Content has been updated. Thanks Jovan.
https://docs.microsoft.com/azure/sql-database/sql-database-features
Column Store index: Azure SQL Hyperscale should be included?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.