With that sort of subscription money, you can get yourself a Chipotle meal or two. Sorry that it's so low, Erik. (Chipotle ads incoming in ......) I appreciate the videos and look forward to seeing you in a couple of days.
Erik - What Query Plan would be used if we asked WHERE (TotalVotes > 10000) versus using the sum of u.UpVotes + u.DownVotes? Would it perform the same Index Seek?
9:50 This always confuses me. How does SQL Server manage to index a column that isn't persisted? How does it index numbers that it doesn't always know?
Well, it “persists” it when it gets indexed by writing the calculated values to index pages and then maintains changing values the way it would maintain any other data changes.
With that sort of subscription money, you can get yourself a Chipotle meal or two. Sorry that it's so low, Erik. (Chipotle ads incoming in ......)
I appreciate the videos and look forward to seeing you in a couple of days.
Ha ha, looking forward to it!
Interesting video, good job)
Thank you kindly! Appreciate the feedback.
3:55 A coverage of the most fun new error messages in SQL Server 2022 would make for a very fun read. Do you have a blog post on this?
I have one from ages ago for messages that were new to SQL Server 2022. I don’t think anything else though.
Erik - What Query Plan would be used if we asked WHERE (TotalVotes > 10000) versus using the sum of u.UpVotes + u.DownVotes? Would it perform the same Index Seek?
As long as TotalVotes is the leading key of an index, yes.
9:50 This always confuses me. How does SQL Server manage to index a column that isn't persisted? How does it index numbers that it doesn't always know?
Well, it “persists” it when it gets indexed by writing the calculated values to index pages and then maintains changing values the way it would maintain any other data changes.