Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • This can help, please read: sqlshack.com/sql-server-execution-plan-operators-part-3
    – sa-es-ir
    Commented Jul 5 at 3:55
  • Rather than images, please share query plans via brentozar.com/pastetheplan. Please also show full tables and index definitions. Commented Jul 5 at 4:19
  • GROUP BY C.categoryid, C.CategoryName might be a good idea, means the compiler can infer uniqueness over the Categories table. Commented Jul 5 at 4:21
  • 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.
    – Ben Thul
    Commented Jul 5 at 15:11