Log File Partition

I am innstalling SQL 2000 Enterprise on Windows 2000 server. I would like
to setup a separate partition for the log file. I would like to know how to
determine the partition size of the log file. Is it acceptable to setup
the partition size of the log file the same partition size as the the
operating system?
Thanks.Thanks for your quick response.
The SQL database will be for the Help Desk and inventory software. We are
going to implement this new software in May. I expect the database to be
10GB by the end of December. I don't expect the database to grow more than
20GB per year. I expect a lot of transaction. My OS partition is 10GB.
Do you install SQL on on OS partition or do you have a separate partition
for SQL?
Please let me know if you need additional information.
Thanks.
"Jeff Duncan" <jduncan@.gtefcu.org> wrote in message
news:02034A00-FCD4-4C27-A7CA-DA1ABAA91571@.microsoft.com...
> Diane
> A lot of that really depends on your DB. Do you expect a lot of
transaction? How large is the DB going to be? How large is your OS
Partition?
> I usually have an 8 gb OS
> and if my Data Partition is around 100 GB
> Then I put my Log Partition around 25 GB.
> But that is my rule of thumb. If you have a lot of transactions that
could be large then you need to adjust accordingly.
> Jeff|||Diane
The standard 3 drive setup is to put the operating system on the C drive, the application(SQL Server in this case) on the D drive and the data on the E drive, in your case the .mdf files would be on E and your .ldf files would be on another drive( F for example).
Ed|||Looks like what you recommend was to setup 4 partitions. I only have two
drives (72.8 GB each) and setup RAID 1.
My OS partition is 10GB. Would you setup the partition for the log file the
same size as your OS partition? In this case, it is 10 GB. Is there a
rule of thumb on how to setup the log file partition?
Thank you.
"Ed" <anonymous@.discussions.microsoft.com> wrote in message
news:D3CAE674-8BFF-4CB0-A920-17C91D4A2093@.microsoft.com...
> Diane,
> The standard 3 drive setup is to put the operating system on the C drive,
the application(SQL Server in this case) on the D drive and the data on the
E drive, in your case the .mdf files would be on E and your .ldf files would
be on another drive( F for example).
> Ed|||I don't quite understand the reasons for the "standard 3 drive setup"? can
someone explain it a bit more for me? (who came up with such "standard"?)
if c is for OS
d is for sql excutables
e is for data, then my questions are:
1. in sql 2k, even specify program files being installed on d, there are
some files still being installed on c:\program files\mssql
2. if all data go to e (both mdf, ldf i assume), is that considered a good
performance (I/O) and fault tolerence (if the d drive gose bad, what happen
to trans log?) strategy?
at my previous company, the set up is
C is for os and sql excutables
D is for logs
and F is for data and backup files.
c and d are one partitioned mirror drive. (for fault tolerance)
F drive is raid 5.
can someone tell me if the "standard 3 drive setup" is better than this set
up? and why?
Steve
"Ed" <anonymous@.discussions.microsoft.com> wrote in message
news:D3CAE674-8BFF-4CB0-A920-17C91D4A2093@.microsoft.com...
> Diane,
> The standard 3 drive setup is to put the operating system on the C drive,
the application(SQL Server in this case) on the D drive and the data on the
E drive, in your case the .mdf files would be on E and your .ldf files would
be on another drive( F for example).
> Ed