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 ...

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 ...

If you don’t have a backup of your MS SQL database, then follow the below ways to recover deleted data. Transaction log files record each change made to the ...

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 ...

I would like to know how transaction log size is managed. I now know after some <BR>reading that I can checkpoint the database in order to allow dirty pages to write from ram to disk.I also know now ...

In the past, the question of how to perform auditing under SQL Server has had a simple answer: Do it yourself. But now, SQL Server 2000 has eased the burden of auditing by introducing an extensive and ...

The next version of Microsoft’s relational database management system (RDMS) promises to bring immense performance gains to online transactional processing systems. SQL Server 2014 will come with a ...

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 ...

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 ...

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 ...