Quantcast
Channel: Answers for "22 GB of log created in SQL Server"
Browsing latest articles
Browse All 8 View Live

Answer by Magnus Ahlkvist

Do you have any idea why the ERRORLOG is growing that big? Are you auditing logins to the ERRORLOG? There's also a case when you use SqlDependency object for handling query notifications in a .NET app...

View Article



Answer by WilliamD

You could also stop sql server, move the error log off the disk that is full and restart sql server. You can then investigate the reason for such a big errorlog file.

View Article

Answer by Fatherjack

can you read the log file to see what is in there? If you cannot cycle the error log then I would guess the drive is completely full. If that is the case then I would look to move/compress other data...

View Article

Answer by ThomasRushton

How long has the server taken to generate 22GB of ErrorLog? If you're not a fan of stopping/restarting your SQL Server (or, more likely, not allowed to...), then you might want to consider setting up a...

View Article
Browsing latest articles
Browse All 8 View Live




Latest Images