I have a development SQL 2000 server system running on Windows 2000 Pro.
I keep this system updated with all production data so I can test
everything.
This question might not be answerable without knowing what kind of data
I have, but I'll ask anyway.
I was thinking about adding a couple of SATA disks to the system. Here
are some possibilities:
1) Leave the log file on its current IDE disk, and set the new SATA
disks up as Raid 0, and put the data file there,
2) Move the log to one of the new SATA disks and the data to the other
SATA disk,
3) Set up the new SATA disks as Raid 0 and put the log and the data both
on the new RAID logical drive that results;
4) Some other arrangement?
It's a 45 GB database that's mostly used for reading (Select queries)
except when I update the database with new transactions and customer
account records daily.
One question...When writing data to a database, is the log file as
active as the data file? Isn't everything written to the log file and
then to the data file?
Thanks for any insight with this very general question.
David WalkerDWalker wrote:
> I have a development SQL 2000 server system running on Windows 2000 Pro.
> I keep this system updated with all production data so I can test
> everything.
> This question might not be answerable without knowing what kind of data
> I have, but I'll ask anyway.
> I was thinking about adding a couple of SATA disks to the system. Here
> are some possibilities:
> 1) Leave the log file on its current IDE disk, and set the new SATA
> disks up as Raid 0, and put the data file there,
> 2) Move the log to one of the new SATA disks and the data to the other
> SATA disk,
> 3) Set up the new SATA disks as Raid 0 and put the log and the data both
> on the new RAID logical drive that results;
> 4) Some other arrangement?
> It's a 45 GB database that's mostly used for reading (Select queries)
> except when I update the database with new transactions and customer
> account records daily.
> One question...When writing data to a database, is the log file as
> active as the data file? Isn't everything written to the log file and
> then to the data file?
> Thanks for any insight with this very general question.
> David Walker
>
Hi David,
All changes are written to the Log first and then to the Data files when
a Checkpoint occours. You could use (3) and leave the System tables on
the IDE disks. This would ensure speed and minimal security (if you
lose the RAID then the system tables are safe on the IDE, if you lose
the IDE then you have most likely lost the OS as well;)
James|||James Wilson <JamesWilson@.bryggemail.dk> wrote in
news:umGxjbwLGHA.3496@.TK2MSFTNGP14.phx.gbl:
> Hi David,
> All changes are written to the Log first and then to the Data files
> when a Checkpoint occours. You could use (3) and leave the System
> tables on the IDE disks. This would ensure speed and minimal security
> (if you lose the RAID then the system tables are safe on the IDE, if
> you lose the IDE then you have most likely lost the OS as well;)
> James
>
OK, thanks for the advice.
David
Showing posts with label raid. Show all posts
Showing posts with label raid. Show all posts
Saturday, February 25, 2012
Data and log files and Raid
I have a development SQL 2000 server system running on Windows 2000 Pro.
I keep this system updated with all production data so I can test
everything.
This question might not be answerable without knowing what kind of data
I have, but I'll ask anyway.
I was thinking about adding a couple of SATA disks to the system. Here
are some possibilities:
1) Leave the log file on its current IDE disk, and set the new SATA
disks up as Raid 0, and put the data file there,
2) Move the log to one of the new SATA disks and the data to the other
SATA disk,
3) Set up the new SATA disks as Raid 0 and put the log and the data both
on the new RAID logical drive that results;
4) Some other arrangement?
It's a 45 GB database that's mostly used for reading (Select queries)
except when I update the database with new transactions and customer
account records daily.
One question...When writing data to a database, is the log file as
active as the data file? Isn't everything written to the log file and
then to the data file?
Thanks for any insight with this very general question.
David Walker
DWalker wrote:
> I have a development SQL 2000 server system running on Windows 2000 Pro.
> I keep this system updated with all production data so I can test
> everything.
> This question might not be answerable without knowing what kind of data
> I have, but I'll ask anyway.
> I was thinking about adding a couple of SATA disks to the system. Here
> are some possibilities:
> 1) Leave the log file on its current IDE disk, and set the new SATA
> disks up as Raid 0, and put the data file there,
> 2) Move the log to one of the new SATA disks and the data to the other
> SATA disk,
> 3) Set up the new SATA disks as Raid 0 and put the log and the data both
> on the new RAID logical drive that results;
> 4) Some other arrangement?
> It's a 45 GB database that's mostly used for reading (Select queries)
> except when I update the database with new transactions and customer
> account records daily.
> One question...When writing data to a database, is the log file as
> active as the data file? Isn't everything written to the log file and
> then to the data file?
> Thanks for any insight with this very general question.
> David Walker
>
Hi David,
All changes are written to the Log first and then to the Data files when
a Checkpoint occours. You could use (3) and leave the System tables on
the IDE disks. This would ensure speed and minimal security (if you
lose the RAID then the system tables are safe on the IDE, if you lose
the IDE then you have most likely lost the OS as well;)
James
|||James Wilson <JamesWilson@.bryggemail.dk> wrote in
news:umGxjbwLGHA.3496@.TK2MSFTNGP14.phx.gbl:
> Hi David,
> All changes are written to the Log first and then to the Data files
> when a Checkpoint occours. You could use (3) and leave the System
> tables on the IDE disks. This would ensure speed and minimal security
> (if you lose the RAID then the system tables are safe on the IDE, if
> you lose the IDE then you have most likely lost the OS as well;)
> James
>
OK, thanks for the advice.
David
I keep this system updated with all production data so I can test
everything.
This question might not be answerable without knowing what kind of data
I have, but I'll ask anyway.
I was thinking about adding a couple of SATA disks to the system. Here
are some possibilities:
1) Leave the log file on its current IDE disk, and set the new SATA
disks up as Raid 0, and put the data file there,
2) Move the log to one of the new SATA disks and the data to the other
SATA disk,
3) Set up the new SATA disks as Raid 0 and put the log and the data both
on the new RAID logical drive that results;
4) Some other arrangement?
It's a 45 GB database that's mostly used for reading (Select queries)
except when I update the database with new transactions and customer
account records daily.
One question...When writing data to a database, is the log file as
active as the data file? Isn't everything written to the log file and
then to the data file?
Thanks for any insight with this very general question.
David Walker
DWalker wrote:
> I have a development SQL 2000 server system running on Windows 2000 Pro.
> I keep this system updated with all production data so I can test
> everything.
> This question might not be answerable without knowing what kind of data
> I have, but I'll ask anyway.
> I was thinking about adding a couple of SATA disks to the system. Here
> are some possibilities:
> 1) Leave the log file on its current IDE disk, and set the new SATA
> disks up as Raid 0, and put the data file there,
> 2) Move the log to one of the new SATA disks and the data to the other
> SATA disk,
> 3) Set up the new SATA disks as Raid 0 and put the log and the data both
> on the new RAID logical drive that results;
> 4) Some other arrangement?
> It's a 45 GB database that's mostly used for reading (Select queries)
> except when I update the database with new transactions and customer
> account records daily.
> One question...When writing data to a database, is the log file as
> active as the data file? Isn't everything written to the log file and
> then to the data file?
> Thanks for any insight with this very general question.
> David Walker
>
Hi David,
All changes are written to the Log first and then to the Data files when
a Checkpoint occours. You could use (3) and leave the System tables on
the IDE disks. This would ensure speed and minimal security (if you
lose the RAID then the system tables are safe on the IDE, if you lose
the IDE then you have most likely lost the OS as well;)
James
|||James Wilson <JamesWilson@.bryggemail.dk> wrote in
news:umGxjbwLGHA.3496@.TK2MSFTNGP14.phx.gbl:
> Hi David,
> All changes are written to the Log first and then to the Data files
> when a Checkpoint occours. You could use (3) and leave the System
> tables on the IDE disks. This would ensure speed and minimal security
> (if you lose the RAID then the system tables are safe on the IDE, if
> you lose the IDE then you have most likely lost the OS as well;)
> James
>
OK, thanks for the advice.
David
Data and log files and Raid
I have a development SQL 2000 server system running on Windows 2000 Pro.
I keep this system updated with all production data so I can test
everything.
This question might not be answerable without knowing what kind of data
I have, but I'll ask anyway.
I was thinking about adding a couple of SATA disks to the system. Here
are some possibilities:
1) Leave the log file on its current IDE disk, and set the new SATA
disks up as Raid 0, and put the data file there,
2) Move the log to one of the new SATA disks and the data to the other
SATA disk,
3) Set up the new SATA disks as Raid 0 and put the log and the data both
on the new RAID logical drive that results;
4) Some other arrangement?
It's a 45 GB database that's mostly used for reading (Select queries)
except when I update the database with new transactions and customer
account records daily.
One question...When writing data to a database, is the log file as
active as the data file? Isn't everything written to the log file and
then to the data file?
Thanks for any insight with this very general question.
David WalkerDWalker wrote:
> I have a development SQL 2000 server system running on Windows 2000 Pro.
> I keep this system updated with all production data so I can test
> everything.
> This question might not be answerable without knowing what kind of data
> I have, but I'll ask anyway.
> I was thinking about adding a couple of SATA disks to the system. Here
> are some possibilities:
> 1) Leave the log file on its current IDE disk, and set the new SATA
> disks up as Raid 0, and put the data file there,
> 2) Move the log to one of the new SATA disks and the data to the other
> SATA disk,
> 3) Set up the new SATA disks as Raid 0 and put the log and the data both
> on the new RAID logical drive that results;
> 4) Some other arrangement?
> It's a 45 GB database that's mostly used for reading (Select queries)
> except when I update the database with new transactions and customer
> account records daily.
> One question...When writing data to a database, is the log file as
> active as the data file? Isn't everything written to the log file and
> then to the data file?
> Thanks for any insight with this very general question.
> David Walker
>
Hi David,
All changes are written to the Log first and then to the Data files when
a Checkpoint occours. You could use (3) and leave the System tables on
the IDE disks. This would ensure speed and minimal security (if you
lose the RAID then the system tables are safe on the IDE, if you lose
the IDE then you have most likely lost the OS as well;)
James|||James Wilson <JamesWilson@.bryggemail.dk> wrote in
news:umGxjbwLGHA.3496@.TK2MSFTNGP14.phx.gbl:
> Hi David,
> All changes are written to the Log first and then to the Data files
> when a Checkpoint occours. You could use (3) and leave the System
> tables on the IDE disks. This would ensure speed and minimal security
> (if you lose the RAID then the system tables are safe on the IDE, if
> you lose the IDE then you have most likely lost the OS as well;)
> James
>
OK, thanks for the advice.
David
I keep this system updated with all production data so I can test
everything.
This question might not be answerable without knowing what kind of data
I have, but I'll ask anyway.
I was thinking about adding a couple of SATA disks to the system. Here
are some possibilities:
1) Leave the log file on its current IDE disk, and set the new SATA
disks up as Raid 0, and put the data file there,
2) Move the log to one of the new SATA disks and the data to the other
SATA disk,
3) Set up the new SATA disks as Raid 0 and put the log and the data both
on the new RAID logical drive that results;
4) Some other arrangement?
It's a 45 GB database that's mostly used for reading (Select queries)
except when I update the database with new transactions and customer
account records daily.
One question...When writing data to a database, is the log file as
active as the data file? Isn't everything written to the log file and
then to the data file?
Thanks for any insight with this very general question.
David WalkerDWalker wrote:
> I have a development SQL 2000 server system running on Windows 2000 Pro.
> I keep this system updated with all production data so I can test
> everything.
> This question might not be answerable without knowing what kind of data
> I have, but I'll ask anyway.
> I was thinking about adding a couple of SATA disks to the system. Here
> are some possibilities:
> 1) Leave the log file on its current IDE disk, and set the new SATA
> disks up as Raid 0, and put the data file there,
> 2) Move the log to one of the new SATA disks and the data to the other
> SATA disk,
> 3) Set up the new SATA disks as Raid 0 and put the log and the data both
> on the new RAID logical drive that results;
> 4) Some other arrangement?
> It's a 45 GB database that's mostly used for reading (Select queries)
> except when I update the database with new transactions and customer
> account records daily.
> One question...When writing data to a database, is the log file as
> active as the data file? Isn't everything written to the log file and
> then to the data file?
> Thanks for any insight with this very general question.
> David Walker
>
Hi David,
All changes are written to the Log first and then to the Data files when
a Checkpoint occours. You could use (3) and leave the System tables on
the IDE disks. This would ensure speed and minimal security (if you
lose the RAID then the system tables are safe on the IDE, if you lose
the IDE then you have most likely lost the OS as well;)
James|||James Wilson <JamesWilson@.bryggemail.dk> wrote in
news:umGxjbwLGHA.3496@.TK2MSFTNGP14.phx.gbl:
> Hi David,
> All changes are written to the Log first and then to the Data files
> when a Checkpoint occours. You could use (3) and leave the System
> tables on the IDE disks. This would ensure speed and minimal security
> (if you lose the RAID then the system tables are safe on the IDE, if
> you lose the IDE then you have most likely lost the OS as well;)
> James
>
OK, thanks for the advice.
David
Friday, February 24, 2012
Data & Log File Location on RAID 5
Hi! I searched for an answer on this, but did not find exactly the info I am looking for . . .
With SQL 2005 I assume it is still appropriate to put data and logs on separate physical drives for best performance. However, I have only one RAID 5 for data and logs. Does it help to put these on separate partitions on the same array for data and logs or should I not even bother since it won't be separate physical disks? Thanks!
Matt, I'm moving your thread to the Database Engine forum where I think you'll get a faster answer.
-Jeffrey
Subscribe to:
Posts (Atom)