THANK YOU, THANK YOU for creating this video on the optimized memory footprint for Compressed Indexes. I have a large client that has a policy about using compression of any kind. Your demonstration of how Compressed Indexes will use less memory (which is always a limited resource) was PERFECT. I've forwarded a link to this video to my client, and I hope that they see (as I do) that Index Compression is a no-brainer. Thanks again!
@@ErikDarlingData And I didn't get a notification of your reply... I think TH-cam stopped liking me because I tried to post a URL in a comment on a previous video of yours. When I log in, I can see more comments than when I log out. In particular, the below is invisible when I log out. "9:08 It took me a while to get my head around Microsoft's white paper on compression. The official docs are pretty useless on this topic, so you need to read the white paper. They said to default to using ROW unless the estimated space savings were super low. Beyond that, they said to use PAGE unless the number of updates (not deletes or inserts, strictly updates) was much higher than anything else that's going on with the table. The CPU cost of PAGE is apparently much higher than that of ROW, but you probably don't want to be thinking about compression at all if you're CPU bound. See also, Test-DbaDbCompression from dbatools. I know of no other good resources on this."
Gang members just don't want be caught calling any dudes Darling...
That’s what cool gang nicknames are for!
THANK YOU, THANK YOU for creating this video on the optimized memory footprint for Compressed Indexes. I have a large client that has a policy about using compression of any kind. Your demonstration of how Compressed Indexes will use less memory (which is always a limited resource) was PERFECT. I've forwarded a link to this video to my client, and I hope that they see (as I do) that Index Compression is a no-brainer. Thanks again!
Ooh, that’s a weird position for them to take! I hope this helps.
On this episode we see Mr Darling’s interpretive dance hand gestures to explain indexy things
It often makes more sense than wordy things.
@@ErikDarlingData i mean the point was to artistically express yourself via hand gestures & dance. you should qualify for the Olympics lol
With the power granted to me by being Italian, I hereby permit you to use our hand gestures. Good luck.
I promise to be a Mario and not a Wario 🤌🍕🍝🇮🇹
Great video post. Thank you Erik.
Yeah! Thank you!
This video was "muy bueno"!
But how many buenos! I need to know!
@@ErikDarlingData Several, at least.
You can be in my gang of taco enthusiasts.
I am currently enthusiastic about tacos.
Came here for the jokes and not disappointed :)
The one thing I never seem to run out of! Thanks for watching!
My comments get deleted automatically on this video!
Weird - I didn’t even see them come through. Usually I get notifications.
@@ErikDarlingData And I didn't get a notification of your reply... I think TH-cam stopped liking me because I tried to post a URL in a comment on a previous video of yours.
When I log in, I can see more comments than when I log out. In particular, the below is invisible when I log out.
"9:08 It took me a while to get my head around Microsoft's white paper on compression. The official docs are pretty useless on this topic, so you need to read the white paper. They said to default to using ROW unless the estimated space savings were super low. Beyond that, they said to use PAGE unless the number of updates (not deletes or inserts, strictly updates) was much higher than anything else that's going on with the table. The CPU cost of PAGE is apparently much higher than that of ROW, but you probably don't want to be thinking about compression at all if you're CPU bound.
See also, Test-DbaDbCompression from dbatools.
I know of no other good resources on this."