I have a SQL dump with very fast file growth. what should I do to stop it?
Dan is correct, when this happens it's almost exclusively some type of corruption or a potential product defect. Much as Dan also points out, form your screenshot it looks as though you're using SQL Server 2008R2 which is entirely out of support.
You have a few options:
- Look at the errorlog and get an idea of the reason for the dumps
- Look at the dump logs to get an idea of the reason for the dumps
- Open up the dumps to find out why the dumps are ocurring
- Blindly run checkdb on all databases
It's impossible to give more help than that given the current set of information in the OP.