best practice for disk paritioning

Can anyone please tell me what the best practice is for SQL 2000 on a
WIndows 2003 server with regards to disk paritioning? My standard setup is
c:/d: on mirrored disk array (c is for OS, d for data) and all other data on
a SAN. What is the best way to configure sql?
What other data is there except data<g>. A logical partition does nothing
for performance if it is on the same drive array as something you are trying
to keep it away from. While C: is great for the OS and SQL Binaries you are
best to place the data and logs on the SAN.
Andrew J. Kelly SQL MVP
"Bad Beagle" <maxwelli@.shaw.ca> wrote in message
news:%23IbisWnzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Can anyone please tell me what the best practice is for SQL 2000 on a
> WIndows 2003 server with regards to disk paritioning? My standard setup
> is c:/d: on mirrored disk array (c is for OS, d for data) and all other
> data on a SAN. What is the best way to configure sql?
>

best practice for disk paritioning

Can anyone please tell me what the best practice is for SQL 2000 on a
WIndows 2003 server with regards to disk paritioning? My standard setup is
c:/d: on mirrored disk array (c is for OS, d for data) and all other data on
a SAN. What is the best way to configure sql?What other data is there except data<g>. A logical partition does nothing
for performance if it is on the same drive array as something you are trying
to keep it away from. While C: is great for the OS and SQL Binaries you are
best to place the data and logs on the SAN.
--
Andrew J. Kelly SQL MVP
"Bad Beagle" <maxwelli@.shaw.ca> wrote in message
news:%23IbisWnzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Can anyone please tell me what the best practice is for SQL 2000 on a
> WIndows 2003 server with regards to disk paritioning? My standard setup
> is c:/d: on mirrored disk array (c is for OS, d for data) and all other
> data on a SAN. What is the best way to configure sql?
>

best practice for disk paritioning

Can anyone please tell me what the best practice is for SQL 2000 on a
WIndows 2003 server with regards to disk paritioning? My standard setup is
c:/d: on mirrored disk array (c is for OS, d for data) and all other data on
a SAN. What is the best way to configure sql?What other data is there except data<g>. A logical partition does nothing
for performance if it is on the same drive array as something you are trying
to keep it away from. While C: is great for the OS and SQL Binaries you are
best to place the data and logs on the SAN.
Andrew J. Kelly SQL MVP
"Bad Beagle" <maxwelli@.shaw.ca> wrote in message
news:%23IbisWnzEHA.260@.TK2MSFTNGP11.phx.gbl...
> Can anyone please tell me what the best practice is for SQL 2000 on a
> WIndows 2003 server with regards to disk paritioning? My standard setup
> is c:/d: on mirrored disk array (c is for OS, d for data) and all other
> data on a SAN. What is the best way to configure sql?
>