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 ...
Transaction logs in Exchange Server are very important. These are not just logs of what happens, transaction logs act as a buffer between the database and the users. Data is temporary kept in ...
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 ...
If it did not, the transaction logs were not deleted after the exchange backup API detected a successful backup. <BR><BR>If you have good SMTP logging enabled on the exchange box, you might be able to ...
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 ...
Lumigent calls this application a "transaction analysis and data recovery solution for Microsoft SQL Server." I call it an essential tool for the SQL Server 7.0 or SQL Server 2000 DBA whose users make ...
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 ...
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 ...
Delayed durability was announced late in the SQL Server 2014 development cycle, but offers something that many SQL Server professionals have wanted for years—the ability to disable transaction logging ...
Some results have been hidden because they may be inaccessible to you
Show inaccessible results