Does the transaction log truncate if you create two separate maintenance plans - one for db backup and one for tran. backup. Is it better to keep them to one maintenance plan? Presently, we have three maintenance plans defined one for full backups of user dbs, one for tran. back of user dbs, and one for system backups. I am considering just leaving the maint. plans at two - system and user and not having a separate one for transaction logs.
Could this pose a problem with truncating logs? Or am I just grasping at straws?
you can define the data backup and log backup seperately in the mainanance wizard, so it should be possible the perform the backups at once. But I wonder what the benefit is of backing up the log file when have just done a full backup (which also contains the transactions that occurred). Isn't it faster when you create a job that only truncates the log file.
Transaction log will be truncated when it reaches the CHECKPOINT if the database is in SIMPLE RECOVERY MODEL or a BACKUP LOG statement referencing the database is executed with either the NO_LOG or TRUNCATE_ONLY clauses.