Yes, That’s A Question
I have no idea if this is a bug or not, but I thought it was interesting. Looking at information added to spills in SQL Server 2016…
If you open the linked-to picture, you’ll see (hopefully) that the full memory grant for the query was 108,000KB.
But the spill on the Sort operator lists a far larger grant: 529,234,432KB.
This is in the XML, and not an artifact of Plan Explorer.
Whaddya think, Good Lookings? Should I file a bug report?
Thanks for reading!
Going Further
For youWork With Your Databases the Way I DoVideo course, $250 until December 1, then $500For your teamAI for Database Teams WorkshopOne day, on-site or remoteOne-on-oneWork With Me for a Day$2,499
Someone still has to know enough SQL Server to keep the robots in check, and that’s what my training is for.

Did you ever figure this one out? I tried to figure out howSQL even calculated that number but I am at a loss.
No, sorry, not yet!