Backup, data and log files

Should data and log files be stored on different drives in
SQL Server 2000. And should the backup files be stored on
yet another drive? I have 2 drives available and have put
the data and log on one and the backup files on the other.
All of these are backed up to tape as well. Thanks.Ideally, your data files should be on one or more drives and log on separate
drives.
It really depends how large your data set is and how important absolute
performance is
to your database. If you have no performance problems with the current setup
and don't
foresee any, then there is no reason to change it.
"Mark" <Mark.Neale@.rspb.org.uk> wrote in message
news:073a01c39f91$5b98ca00$a601280a@.phx.gbl...
> Should data and log files be stored on different drives in
> SQL Server 2000. And should the backup files be stored on
> yet another drive? I have 2 drives available and have put
> the data and log on one and the backup files on the other.
> All of these are backed up to tape as well. Thanks.|||Its better to have log on different drive and db on different if it is
largely growing db
--
Shaju Thomas
e-Cosmos Technologies Ltd.,
Mail: shaju@.e-cosmostech.com
Phone(Off) : 51217038/39 Extn: 132
Mobile: +91 98455 21794
"Mark" <Mark.Neale@.rspb.org.uk> wrote in message
news:073a01c39f91$5b98ca00$a601280a@.phx.gbl...
> Should data and log files be stored on different drives in
> SQL Server 2000. And should the backup files be stored on
> yet another drive? I have 2 drives available and have put
> the data and log on one and the backup files on the other.
> All of these are backed up to tape as well. Thanks.|||On Fri, 31 Oct 2003 01:28:35 -0800, "Mark" <Mark.Neale@.rspb.org.uk>
wrote:
>Should data and log files be stored on different drives in
>SQL Server 2000. And should the backup files be stored on
>yet another drive? I have 2 drives available and have put
>the data and log on one and the backup files on the other.
>All of these are backed up to tape as well. Thanks.
If you had the money to spend, a general baseline suggestion would be
data on one drive, transaction log on another, and backups on yet
another... however, the "yet another" would probably be better if it
was a network share.
Separating the DB file and the transaction log helps with performance,
if you're using SCSI drives.(It might also help with performance if
you are using IDE drives, and each drive is on a separate IDE channel,
however, I can not make any guarantee on this. I *can* guarantee that
it won't do jack for performance if you have two separate IDE drives
on the same IDE channel.)
Separating the backup from both helps with reliability; if your
backups are on your database or transaction log disk, and that disk
dies, you've lost both. Putting the backups on another machine also
means you can restore from backup without having to retrieve a drive
from the machine that crashed.
Of course, you can get even better, more expensive, setups if you want
them... this is just the baseline.