Search Results
| 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 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| 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 index
Search options not deleted
user 9294
A database structure that can improve the speed of queries at the cost of disk space and slower inserts/updates. It stores a copy of one or more columns sorted but structures the data differently to allow faster access.
2
votes
0
answers
92
views
work/cache table issues, heavy inserts with heavy reads
We have tracked this down to index splits. here are some questions:
1) The primary key is an auto number and a bunch of other columns. The auto number is first in order. … Does this mean all entries will always be added to the end of index resulting in new leafs and not splits, therefore we do not need to worry about setting a lower fill factor? …
- 289