May 26, 2009 at 12:55 pm
There's a wizard for the maintenance plan you can use. Just choose log backups to not mess up anything else you have running.
May 26, 2009 at 1:11 pm
So if I back up the lgos regularly, it will make the logs smaller?
May 26, 2009 at 1:18 pm
middletree (5/26/2009)
So if I back up the lgos regularly, it will make the logs smaller?
In theory, yes. By running regularly scheduled transaction log backups, you will keep the size of the transaction log from continually growing. The transaction log backup will allow SQL Server to reuse space in the transaction log instead of having to continually grow to store additional log records.
Unexpected activities or one off processes may affect this.
May 26, 2009 at 1:26 pm
middletree (5/26/2009)
So if I back up the lgos regularly, it will make the logs smaller?
More correct to say, if you backup the logs frequently the log shouldn't grow. A backup won't make the log smaller.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 26, 2009 at 1:36 pm
The log backup clears space from the existing log so that it can be reused. It clears the space of the transactions that are in the log backup.
So if you have more frequent log backups, you can have a smaller log file. Less frequent, bigger log file.
Frequency doesn't change disk requirements much as you still back up the same information.
Viewing 5 posts - 31 through 34 (of 34 total)
You must be logged in to reply to this topic. Login to reply