CallwaveEmp
Technical User
- Aug 30, 2002
- 106
Hi All.
We have been configuring our Larger SQL Servers with the following disk
layout:
c:\ OS
d:\ SQL Server Executables
e:\ Database Files, tempdb.
f:\ Database Logs.
I would like to adjust this a bit by using junction points to link folders
on E and F back to the D:\...\MSSql, then place the database files in these
folders. The files will still be on different disks, however, as far as SQL
Server is concerned, the files will be stored in D:\...\mssql\TDATA an
D:\...\mssql\TLog. This will alow us to standardize our configurations
better - we can move files to a SAN, or other DAS, but the SQL Server
configurations are the same.
A developer in our group claims that without the files explicitly being on a
different drive ("E:/F:") SQL Server will not paralellize the queries, and
we will lose performance. I am hoping that this is incorrect, can anyone
confirm?
Dave
We have been configuring our Larger SQL Servers with the following disk
layout:
c:\ OS
d:\ SQL Server Executables
e:\ Database Files, tempdb.
f:\ Database Logs.
I would like to adjust this a bit by using junction points to link folders
on E and F back to the D:\...\MSSql, then place the database files in these
folders. The files will still be on different disks, however, as far as SQL
Server is concerned, the files will be stored in D:\...\mssql\TDATA an
D:\...\mssql\TLog. This will alow us to standardize our configurations
better - we can move files to a SAN, or other DAS, but the SQL Server
configurations are the same.
A developer in our group claims that without the files explicitly being on a
different drive ("E:/F:") SQL Server will not paralellize the queries, and
we will lose performance. I am hoping that this is incorrect, can anyone
confirm?
Dave