sql server - Usefulness of separating database files and trans logs among partitions -


Some people are working on a new database server for SQL Server where I work. The server also has a system drive that stores backups for single database files and also stores single RAID 5 arrays. RAID 5 array is logically divided into 2 drives. Is for a real database files (MDF) and for the second transaction log (LDF). The reason quoted is best practice.

My question is whether or not this extra division is redundant or not. Is there any purpose for different logical partitions with databases and trans-losses if they are still sharing the same physical resource? I understand that there are a few big reasons for the two physically separate disks to separate the database and trans log files. For example, speed and disaster recovery should be improved. However, I can not think of any benefit which is not denied by the lack of physical separation. I'm not sure enough to know about that.

You are too much on the mark. The only such other situation that may be wrong is a corruption of corruption, and they are incredibly rare (and probably catered for your red hardware).

I think it is easy to talk about separating data files from log files (or, in fact, different drives different drives Instead of referencing different spindles , separating the filegroup for table-reading parallelism) makes it more clear to people who have little information and know it dangerously :) < / P>


Comments

Popular posts from this blog

c++ - Linux and clipboard -

Visual Studio 2005: How to speed up builds when a VSMDI is open? -

booting ubuntu from usb using virtualbox -