Posted by Mike Epprecht \(SQL MVP\) on 12/20/05 21:52

Hi

SQL Server uses only one virtual log file per database at a time, so having
multiple transaction log files will not help.

Transaction logs are only a performance problem when they are not on disks
that are optimal for them. As they are sequential writes, RAID-10 is best,
and on separate drives to the database files so the IO is not shared by data
reads.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

<plsullivan63@gmail.com> wrote in message
news:1135105221.803070.50000@g43g2000cwa.googlegroups.com...
> Is a single transaction log created for a database or, if you have a
> primary and a secondary file group in that database, are two
> transaction logs generated? Yep, a newbie.
> Thanks,
> Phil
>

• Next in forum: Re: one transaction log per filegroup?
• Prev in forum: Re: one transaction log per filegroup?
• Thread view: Re: one transaction log per filegroup?

[Reply to this message]