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 ...
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 ...
The transaction log file contains the SQL Server transactions of the database. It basically records the database transactions and the changes made by the transactions to the database. The logs are ...
So I'm trying to figure out when I should be backing my transaction logs relative to my full/diffs. It seems like right after would be when I'd want to have the checkpoint happen, or does it really ...
Elaborate backups might seem like a good idea at first, but they add unnecessary complexity to your recovery process. Here are some things to keep in mind to make backup and recovery as smooth as ...
There isn’t a week that goes by that I don’t hear or read about an organization seeing ginormous transaction log (.ldf) files, while the associated data (.mdf) file is at the size it should be when ...
Microsoft has two primary platform as a service (PaaS) offerings for SQL Server running Azure: Azure SQL Database, which is primarily used for new applications that were developed and grown in the ...
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 ...
What do you do when you can't avoid huge transaction logs in SharePoint and your files are too large? Last month, I wrote about how to avoid having ginormous transaction logs within SharePoint ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results