>Anyone knows why the shrink log sometimes will shrink the log at 1 MB and sometimes to a higher number? On my databases, this is always 1 MB. But, on a client's database, this puts it down to 359 MB. There has to be a setting which controls that. Anyone would know what it is?
If your recovery model is "Full" you must have full backup of the database and backup of the LOG to shrink the file.
BTW there is no need to shrink the LOG.
Autogrowth is a resource eating task. If you Backup the LOG SQL Server can reuse its space.
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.
