(The Curious Case of… used to be part of our bi-weekly newsletter but we decided to make it a regular blog post instead so it can sometimes be more frequent. It covers something interesting one of us encountered when working with a client, doing some testing, or were asked in a random question from the community.)
We had an interesting case with a client last week where one of their SQL Server instances was creating memory dumps. Jonathan investigated the memory dumps and all of the call stacks pointed to memory corruption, however there were no 832 errors in the error log. Why not?