A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.
Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options answers only user 151544
1
vote
That sounds like a strange case for a columnstore index. Anyhow: 1: For a columnstore index you get the compression of data, as well as posslibly segment elimination. But there are no such thing as … a seek in a columnstore index. So, if you have queries with high selectivity searching on those columns and preformance is important, then yes - having row indexes (that comes with PK and UQ) can be …
answered Sep 11 '18 by Tibor Karaszi
2
votes
"How it is possible to have only 1 lob physical read with cold cache if the table has about 470 million records?" Because the other physical reads were served by read-ahead (the LOB type). Perhaps th …
answered Aug 30 '19 by Tibor Karaszi
4
votes
There would be little meaning to allow for this. The columns aren't ordered in the index anyhow. Just include all columns that you want in the one and only col-store index that you can have (or if it …
answered Sep 27 '18 by Tibor Karaszi