Re: one transaction log per filegroup?
- From: "Mike Epprecht \(SQL MVP\)" <mike@xxxxxxxxxxxx>
- Date: Tue, 20 Dec 2005 20:52:40 +0100
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@xxxxxxxxxxxx
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<plsullivan63@xxxxxxxxx> wrote in message
news:1135105221.803070.50000@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> 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
>
.
- Follow-Ups:
- Re: one transaction log per filegroup?
- From: plsullivan63
- Re: one transaction log per filegroup?
- References:
- one transaction log per filegroup?
- From: plsullivan63
- one transaction log per filegroup?
- Prev by Date: Re: How to pass table names to a Stored procedure
- Next by Date: Re: time format error
- Previous by thread: one transaction log per filegroup?
- Next by thread: Re: one transaction log per filegroup?
- Index(es):
Relevant Pages
|
