barnesco
asked on
Why install SQL binaries on another drive
I know it's best practices to install SQL binaries on a non-system drive, but (the ugly truth), I don't know why. A client asked me and I'm er, uh...just because....
So why should SQL binaries be installed on a drive other than the OS as best practices? Google isn't giving up much.
So why should SQL binaries be installed on a drive other than the OS as best practices? Google isn't giving up much.
I'm not going to lie - I always install the binaries on the system drive. I believe the TempDB (all system DBs, for that matter) installs wherever the DBE is installed by default, which can be problematic if it expands to a point where it brings your drive down. Beyond the concern that OS I/O causing disk contention that would impact SQL disk throughput, and the previously mentioned reason, I can't think of anything else. Data and log files go on there own separate drives, definitely.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The two answers above make perfect sense. Thanks.
It might be a technicality, but I think the correct answer should be awarded to x66_x72_x65_x65 and mine should be only an assist. I feel his/hers is more accurate.