Our normal practices for backing up SQL servers is to use the regular SQL backup tools to perform full, differential and transaction log backups and this has always worked fine. Recently we performed ...

In an earlier blog entry, I talked about “Deprecated” code and I highlighted the fact that the BACKUP LOG WITH NO_LOG and BACKUP LOG WITH TRUNCATE_ONLY statements are no longer allowed in SQL Server ...

Well, I already mentioned the need to periodically back up the transaction logs, which also purges the contents of the log files and avoids the monster-sized log files. The following diagram is an ...

We have the following set up on our SQL servers:<BR><BR>Recovery model is full (for dbs being backed up)<BR>A full backup of the specified database Mon - Fri, no Transaction log backup included in the ...

Help! My SQL Server Log File is too big!!! Your email has been sent Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim ...

In Exchange Server, transaction logs act as a buffer storage between the user, memory, and database. Transaction logs are generated constantly and purged after a successful backup of the database. If ...