No. A full backup alone won't shrink the log file. All it does, is remove not longer used entries, thus making "room" for new entries. It does not touch the size. This is your responsibility, but have a look around here. Shrinking the log file without an immediate need is not really recommended.
Hi Small correction in last reply i mentioned as increase the Log file sorry to decrease the log file.
[quote user="FrankKalis"] No. A full backup alone won't shrink the log file. All it does, is remove not longer used entries, thus making "room" for new entries. It does not touch the size. This is your responsibility, but have a look around here. Shrinking the log file without an immediate need is not really recommended. [/quote] I believe that unless the database is in simple recovery model or a transaction log backup is taken transaction log file cannot be shrink. BACKUP LOG WITH TRUNCATE_ONLY internally changes the recovery model into simple and then changes back.
[quote user="FrankKalis"] No. A full backup alone won't shrink the log file. All it does, is remove not longer used entries, thus making "room" for new entries. It does not touch the size. This is your responsibility, but have a look around here. Shrinking the log file without an immediate need is not really recommended. [/quote] I believe that unless the database is in simple recovery model or a transaction log backup is taken transaction log file cannot be shrink. BACKUP LOG WITH TRUNCATE_ONLY internally changes the recovery model into simple and then changes back.
HI Shawn. if want to increase the Log file size you can keep your Database recovery model a Simple. this can be done when your not performing the LogShipping of that particular Database.One more thing inplace of shrinking the Log file you can truncate if you required.
Unless if there is a problem with disk space or immediate need to reduce the backup size, I wouldn't recommend SHRINK of log file and even DATA file...its a evil and works negative way on the performance.