I had that a while back. Seemed pretty weird at the time, and I asked about it on [dba.se](https://dba.stackexchange.com/questions/35595/how-might-a-corrupt-partition-in-tempdb-result-in-dbcc-checkdb-reporting-no-issu)
there are some decent options for recording from both sides detailed [here](https://blog.podcast.co/create/record-podcasts-remotely)
I would record it from both ends, then send the file to Erik to process it using multiple tracks. Then you wouldn't get dropouts from Internet connectivity issues, etc.
I've listened to them and assumed it was because I was old. It seems like it needs a bit more treble and a little less bass or something.
interesting post - I wonder why it needs to do that. Perhaps something about redo/recovery for the affected index being easier with the data in the log.
No, though I expect them to Google it. Am I really writing for other people though?
as a professional, what does "really hard to understand" actually mean in terms of practical matters
Comment: Podcast was very inspiring and somewhat helpful, thank you for sharing it. Sadly, Joe was really hard to understand.
first post in nearly a year https://forrestmcdaniel.com/2024/04/08/included-columns-cause-log-bloat/
yeah, i'm not sure a venn diagram is going to be good at showing that. you might need a different vehicle, like a flow chart or something.