just like that, i'm probably done thinking about scalabilty strategies for #sqlserver, and back to investigating latch timeouts on very busy systems. 
here's the thing. the number of mdmp files for a given large-memory system can be pretty small, especially if an Availability Group is involved.
while a dump is in progress, #sqlserver memory must remain in a constant consistant state. the more memory, the longer the dump may take (there are other un-enumerated factors).
but, Availability Group lease timeout can only be set as high as 100 seconds currently.
but, Availability Group lease timeout can only be set as high as 100 seconds currently.
so a latch timeout followed by a diagnostic memory dump on a large-memory system has a chance to result in lease timeout and a disruption for the AG.
and if it happens once, it can happen after every #sqlserver service restart.
and if it happens once, it can happen after every #sqlserver service restart.
thankfully, after a given latch timeout dump signature is encountered, the next such dump opportunity will not generate a dump. until the next #sqlserver service restart.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
