Overgrown transactional log files can turn into real problems if they are not handled properly. Today SQL Server consultant Tim Chapman discusses the perils of not handling SQL Server log growth ...

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is ...

The log files you speak of are actually the transaction logs - what SQL uses to actually accept changes to the database.

Delayed durability offers something that many SQL Server professionals have wanted for years-the ability to disable transaction logging. Why turn off the transaction log? You can accelerate ...

The obvious examples include Windows Server logs, Exchange application logs, SQL logs, logs from any ODBC-compliant database (such as Oracle, IBM DB2, Informix and MySQL) and any ASCII-based .TXT ...

Looking forward to some new hardware for our existing SQL 2005 Server next year. I believe traditional thinking has it that you should have 3 spindles/arrays, one each for: OS, Logs and Data and ...

The recent versions of Microsoft SQL Server include several high-availability solutions like failover clustering, database mirroring, log shipping and replication.

ChaosSearch adds support for SQL to a log analytics platform that stores data natively in object-based storage systems in the cloud.

SQL Server, of course, keeps track of everything that affects data in a transaction log, which is periodically rolled over into backup files (at least, if you're being a conscientious DBA it is). But ...