Timeline for SAN for SQL Server: One large spindle set for all loads, or discrete by load?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 17, 2022 at 9:09 | comment | added | variable | Log disk access won't be sequential on the disk given that there will be more than 1 db. Each db's log file will be sequentially written but collectively the disk will behave like random access when there is more than 1 db. | |
| Feb 27, 2016 at 0:40 | vote | accept | Jonesome Reinstate Monica | ||
| Feb 23, 2016 at 4:31 | answer | added | Jonesome Reinstate Monica | timeline score: 1 | |
| Feb 19, 2016 at 6:27 | history | edited | Paul White♦ |
edited tags
|
|
| Feb 19, 2016 at 4:44 | history | edited | Jonesome Reinstate Monica | CC BY-SA 3.0 |
added 56 characters in body
|
| Feb 19, 2016 at 3:33 | comment | added | Aaron | Maybe helpful RAID 10 | |
| Feb 19, 2016 at 3:26 | comment | added | Aaron | One thing to take into account is that log files write sequentially and mixing them with the data files you are going to force all of the disk io to be random. I've worked with Dell on my server and they told me similar things, but they also didn't disclose that some of the performance they referred to required buying the licensing for the optional features on the disk shelves. I'm also running all SSDs so the traditional thinking for layout of the files on the disk systems doesn't fully apply but with HDD I still feel they do. | |
| Feb 19, 2016 at 0:58 | answer | added | Ali Razeghi - AWS | timeline score: 2 | |
| Feb 19, 2016 at 0:03 | history | asked | Jonesome Reinstate Monica | CC BY-SA 3.0 |