Hi, In my humble opinion, and based on the fact you have numerous hard disks/disk arrays for partitioning, the best partitioning scheme for MS-SQL is the following: One partition for OS (C) One partition for the SYS_DB (D) One partition for the DB files (E) One partition for the DB_LOG files (F) One partition for the TEMP_DB files (G) One partition for the TEMP_LOG_DB files (H) In this manner you can separate database from log files that will allow you to perform point in time recovery in case DB crashes. Moreover, separate disks allow optimized I/O thus increase performance. What is your opinion on the case?

New posts

Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED Best Partitioning Scheme for stand alone MS-SQL (stabitily & performance)

Thread starter sip03ds
Start date May 20, 2018
Replies 0
Views 2K
Tags

sql server

sip03ds

New Member

May 20, 2018

Hi,

In my humble opinion, and based on the fact you have numerous hard disks/disk arrays for partitioning, the best partitioning scheme for MS-SQL is the following:

One partition for OS (C)
One partition for the SYS_DB (D)
One partition for the DB files (E)
One partition for the DB_LOG files (F)
One partition for the TEMP_DB files (G)
One partition for the TEMP_LOG_DB files (H)

In this manner you can separate database from log files that will allow you to perform point in time recovery in case DB crashes.
Moreover, separate disks allow optimized I/O thus increase performance.

What is your opinion on the case?