Timeline for How to use the right index to optimize a database to get rid of unwanted hash matches?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5 at 15:11 | comment | added | Ben Thul | I don't have any specific advice for you here. But I would like to introduce you to one of my favorite games. It's called "what's that knob for?". It's played when some so-called "best practice" says that something's bad. But! if it were always bad, it wouldn't be in the product, right? So the game is determining under what circumstances that thing isn't bad. | |
| Jul 5 at 13:14 | history | edited | The Impaler |
edited tags
|
|
| Jul 5 at 6:59 | answer | added | SQLpro | timeline score: 0 | |
| Jul 5 at 4:21 | comment | added | Charlieface |
GROUP BY C.categoryid, C.CategoryName might be a good idea, means the compiler can infer uniqueness over the Categories table.
|
|
| Jul 5 at 4:19 | comment | added | Charlieface | Rather than images, please share query plans via brentozar.com/pastetheplan. Please also show full tables and index definitions. | |
| Jul 5 at 3:55 | comment | added | sa-es-ir | This can help, please read: sqlshack.com/sql-server-execution-plan-operators-part-3 | |
| Jul 5 at 3:32 | history | edited | Iker-JK | CC BY-SA 4.0 |
added 1 character in body
|
| Jul 5 at 3:31 | history | edited | Iker-JK | CC BY-SA 4.0 |
added 5 characters in body
|
| S Jul 5 at 3:22 | review | First questions | |||
| Jul 5 at 7:08 | |||||
| S Jul 5 at 3:22 | history | asked | Iker-JK | CC BY-SA 4.0 | created from wizard |