The log file was set at 50 meg and would use 5 to 15 meg and the other 45 to 35 meg would remain unused.
Significant changes were made to the SQL database that required a lot of I/O. This caused the log file to spike to 800 meg and after the significant changes were complete, the log file was left at 700 meg unused and 100 meg used.
Because I know what event caused it to grow to 800 meg should I shrink it back to the previous 50 meg instead of leaving it at 800 meg? A second question is why does it keep 100 meg as used when previously it would many times leave 5 meg to 15 meg as used? Does a 800 meg log file only parse itself into increments of around 100 meg so it will always consider 100 meg to be used?
Is there a command similiar to DBCC SHRINKDATABASE (EPDB, 50) but for Log files?