Joe_Budden
asked on
MSDE, transaction logs and partitions
Hi
We have an application that runs on Windows 2008 servers. It requires a DB so we'll also have MSDE installed on the same box.
I understand that it's generally better to have transaction logs on RAID 1 and the database on RAID 5.
We could have the transaction logs on the same RAID group as the C drive in that case.
C: OS and transaction logs
D: Application and MSDE database
However, is there any issue with having two write intensive 'applications' (the OS and the transaction logs) on the same partition?
Also, I guess there is a higher risk placing them on the C drive in case the logs fill up the C drive and knock the server over?
What are people's recommendations?
We have an application that runs on Windows 2008 servers. It requires a DB so we'll also have MSDE installed on the same box.
I understand that it's generally better to have transaction logs on RAID 1 and the database on RAID 5.
We could have the transaction logs on the same RAID group as the C drive in that case.
C: OS and transaction logs
D: Application and MSDE database
However, is there any issue with having two write intensive 'applications' (the OS and the transaction logs) on the same partition?
Also, I guess there is a higher risk placing them on the C drive in case the logs fill up the C drive and knock the server over?
What are people's recommendations?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
also, for write intensive applications you should look at RAID 10 instead of RAID 5
ASKER
Thanks! Out of interest, what's the reason for never placing transaction logs on the C drive?
it's bad practice,
t-logs should be placed on their own spindle, outside of the OS.
Also, for fault tolerance, you want them on a separate disk in the case of a disaster happening.
Performance gains when placed outside of OS drive.
t-logs should be placed on their own spindle, outside of the OS.
Also, for fault tolerance, you want them on a separate disk in the case of a disaster happening.
Performance gains when placed outside of OS drive.
ASKER
Thanks..
As regards to placing t logs on their own drive, does this include when circular logging is enabled?
As regards to placing t logs on their own drive, does this include when circular logging is enabled?
the actual t-logs is circular logging anyway, but still, should always be placed separately to data fils.
ASKER
Ah ok.... I thought t logs were only flushed with a full backup ?
by ciruclar log, it's not automatic.....
yes, you need to truncate the log essentially for it to wrap around.
Doing a transaction log backup within SQL will do this.
yes, you need to truncate the log essentially for it to wrap around.
Doing a transaction log backup within SQL will do this.