August 8, 2006 at 8:15 am
Hi All,
I currently have my database set up as follows:
Drive F: (SAN , Capacity = 800GB)
I have the data file of my main database
I also have the transaction log on thesame drive.
NB: My transaction log file doesnt normally exceed 10GB
Drive G: (Local drive, RAID 5 (I think) Capacity 60GB)
Tempdb & Other system Databases
I am looking to move the transaction log file onto drive G, with the hope that my database can become faster.
would it be wise to move the log onto drive G: as I use a simple recovery model and my Manager isnt willing to shell our money for a seperate disk for the transaction log, raid (1 or 10) I would have preferred.
What can I do now, move it to drive G: or leave it on F:
Thanks in advance.
John
August 8, 2006 at 8:32 am
I am not a SAN expert but my understanding is that it depends how your SAN is organised.
My understanding is that RAID5 is slow for writing (because of its striping of data) but faster for reading so I am not sure if you will gain some performance benefits.
If you are looking to get a performance boost then try placing your log files in FULL or BULK LOGGED recovery mode then clear them down each night with a BACKUP LOG yourdb WITH TRUNCATEONLY.
In SIMPLE mode SQL Server will clear down the logs when they become 70% full of committed transactions so you have the overhead of this activity.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply