Custom Install

I'm installing SQL for the first time in my Lab and I'm using the
Microsoft SQL 2000 Training kit. During the custom install I have the
option to install the Program files and the Data files in separate
partitions however no where in the book does it suggest that either
partition would be the optimal location for performance reasons. It
seems to me that separating the program files from the data files
makes more sense. If I had a production server with 200 or 300GB in a
Raid array I don't think I would make one big system partition and
install the whole thing on it. But thats why I'm asking, what say you
all? What do the Pros do?
Tia
ScottThe important thing is where you later create your database files for your production databases. The
program files are largely irrelevant as are the system database's files (except perhaps tempdb). In
general, put the transaction log file(s) on its own RAID1 and the database on RAID 10, 01 or
possibly 5.
There are plenty written on that topic. One place you could start is: www.sql-server-performance.com
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"scott abra" <scott_abra@.hotmail.com> wrote in message
news:44e8e747.0310231516.41503a97@.posting.google.com...
> I'm installing SQL for the first time in my Lab and I'm using the
> Microsoft SQL 2000 Training kit. During the custom install I have the
> option to install the Program files and the Data files in separate
> partitions however no where in the book does it suggest that either
> partition would be the optimal location for performance reasons. It
> seems to me that separating the program files from the data files
> makes more sense. If I had a production server with 200 or 300GB in a
> Raid array I don't think I would make one big system partition and
> install the whole thing on it. But thats why I'm asking, what say you
> all? What do the Pros do?
> Tia
> Scott