Timeline for How can I improve the performance of this query on a table with millions of trigrams?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2020 at 23:12 | vote | accept | Interminable | ||
| Apr 13, 2020 at 23:12 | comment | added | Interminable | Unfortunately we're operating on a tiny budget right now so can't go to Premium for columnstore indexes, but the information is much appreciated! It may be useful in the future, and hopefully to others as well! | |
| Apr 13, 2020 at 13:59 | history | edited | Josh Darnell | CC BY-SA 4.0 |
added 460 characters in body
|
| Apr 13, 2020 at 1:21 | comment | added | Conor Cunningham MSFT | Paul's article is very good. Since then, we added batch mode on rowstore in the more recent compat levels so please consider that - it will provide more benefit at higher DOPs, however. Also, a columnstore index may be an experiment to consider if you don't want to go all the way to what Paul has done. It may give you some of the benefit at lower CPU (and it uses batch mode as well). No promises it will make your exact scenario faster, but it is worth trying as an experiment. | |
| Apr 10, 2020 at 13:55 | history | answered | Josh Darnell | CC BY-SA 4.0 |