Timeline for Optimize BETWEEN Query in SQL Server Azure
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2021 at 12:14 | comment | added | Stephen Morris - Mo64 | Hi Tibor what I meant was - If you order the data with a regular clustered index and then build the columnstore index with the drop_existing clause you can get ordering in your columnstore - proviso you need maxdop 1. One of Nico's blogs explains it nikoport.com/columnstore (but I didn't have time to search through all 131 entries). | |
| Apr 12, 2021 at 12:11 | comment | added | Tibor Karaszi | There's no ORDER clause when you create a columnstore index for the regular SQL Server. So you would have to make sure that SQL Server "happens" to read the data in the order that would match the segment elimination. I believe that Hugo wrote about it here: sqlservercentral.com/steps/… | |
| Apr 12, 2021 at 10:10 | vote | accept | Spaceguy152 | ||
| Apr 12, 2021 at 8:00 | comment | added | Stephen Morris - Mo64 | this technique should work in all flavours of MS SQL | |
| Apr 12, 2021 at 7:58 | comment | added | Spaceguy152 | Thanks for this. I was wondering if it's possible to order the Columnstore indexes in Azure SQL Server or is this possible only in Azure data warehouse? | |
| Apr 12, 2021 at 7:27 | history | answered | Stephen Morris - Mo64 | CC BY-SA 4.0 |