Forum Discussion
SQL Server 2019 over running disk space
MSSQL DATA is exceeding disk usage. It seems there would be a way to limit data base impact on hard drive. Attempts to limit in autogrowth section are being overwritten somewhere and and locking the ...
Thank you for your response. If we backup the log file, won't the hard drive still have all the data and be over run?
What good is the log file? Is it necessary? We are gathering log file size about 1 gig a minute. Something just doesn't seem like we have it set up right on the front end?
The predominant file is SQLDump####.mdmp "Crash Dump File". We get ten 17mb files of this type a minute. dropping into our MSSQL>Log file.
Question 1 is not clear for me. As I wrote, log backup releases VLF = "Virtual Log Files" for re-use, it don't shrink the file; see https://learn.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-shrinkfile-transact-sql?view=sql-server-ver16
The transaction log is mandatory.
Dump files are created if a process crashes and that's not good. Install latest SQL Server updates (see https://sqlserverbuilds.blogspot.com/). If it still occurs, raise a case at MS Support.
The transaction log is mandatory.
Dump files are created if a process crashes and that's not good. Install latest SQL Server updates (see https://sqlserverbuilds.blogspot.com/). If it still occurs, raise a case at MS Support.