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

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

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

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

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