Quantcast
Channel: Answers for "22 GB of log created in SQL Server"
Viewing all articles
Browse latest Browse all 8

Answer by Fatherjack

$
0
0
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 to give you a few MB free to cycle the error log and then you can remove/compress/investigate the huge log.

Viewing all articles
Browse latest Browse all 8

Trending Articles