Hi !
We have a sql server 2000, IIS and windows 2000 op-sys.
1133 Mhz cpu, 512 Mb RAM, raid5 scsi disk.
One prod database size 1164 Mb
Two test databases size 45 Mb
The server have 4 user in production and 1 programmer.
Is this server to small ?
If yes, what should we upgrade ?
Regards Jan RockstedtConsidering that your database and number of users is within the limitations
for MSDE (2GB data, 5 concurrent users), and MSDE is designed to run on a
desktop machine, I would say that your server might be overspec'd rather
than underspec'd.
Do you have any performance issues with it?
--
Jacco Schalkwijk
SQL Server MVP
"Jan" <_NO_SPAM_@.telia.com> wrote in message
news:O2LAncL8DHA.1548@.tk2msftngp13.phx.gbl...
> Hi !
> We have a sql server 2000, IIS and windows 2000 op-sys.
> 1133 Mhz cpu, 512 Mb RAM, raid5 scsi disk.
> One prod database size 1164 Mb
> Two test databases size 45 Mb
> The server have 4 user in production and 1 programmer.
> Is this server to small ?
> If yes, what should we upgrade ?
> Regards Jan Rockstedt
>|||I have problem with the RAM.
The server is allocating 560 Mb of 512 Mb, and using the swap file.
Is the any recomendation of memory alocating in SQL server 2000 ?
//Jan
Jacco Schalkwijk wrote:
> Considering that your database and number of users is within the
> limitations for MSDE (2GB data, 5 concurrent users), and MSDE is
> designed to run on a desktop machine, I would say that your server
> might be overspec'd rather than underspec'd.
> Do you have any performance issues with it?
>
> "Jan" <_NO_SPAM_@.telia.com> wrote in message
> news:O2LAncL8DHA.1548@.tk2msftngp13.phx.gbl...
>> Hi !
>> We have a sql server 2000, IIS and windows 2000 op-sys.
>> 1133 Mhz cpu, 512 Mb RAM, raid5 scsi disk.
>> One prod database size 1164 Mb
>> Two test databases size 45 Mb
>> The server have 4 user in production and 1 programmer.
>> Is this server to small ?
>> If yes, what should we upgrade ?
>> Regards Jan Rockstedt|||F.Y.I the sql server i configure:
Dynamically configure SQL server memory
Minimum 41 MB
Maximum 388 MB
Minimum query memory (KB) 1024
Jan wrote:
> I have problem with the RAM.
> The server is allocating 560 Mb of 512 Mb, and using the swap file.
> Is the any recomendation of memory alocating in SQL server 2000 ?
> //Jan
> Jacco Schalkwijk wrote:
>> Considering that your database and number of users is within the
>> limitations for MSDE (2GB data, 5 concurrent users), and MSDE is
>> designed to run on a desktop machine, I would say that your server
>> might be overspec'd rather than underspec'd.
>> Do you have any performance issues with it?
>>
>> "Jan" <_NO_SPAM_@.telia.com> wrote in message
>> news:O2LAncL8DHA.1548@.tk2msftngp13.phx.gbl...
>> Hi !
>> We have a sql server 2000, IIS and windows 2000 op-sys.
>> 1133 Mhz cpu, 512 Mb RAM, raid5 scsi disk.
>> One prod database size 1164 Mb
>> Two test databases size 45 Mb
>> The server have 4 user in production and 1 programmer.
>> Is this server to small ?
>> If yes, what should we upgrade ?
>> Regards Jan Rockstedt|||If you want to avoid having the server use the page file (I guess that's
mostly IIS that does that) you can limit SQL Server to 340 MB or less, or
you can buy some more memory. Memeory is quiet cheap these days.
--
Jacco Schalkwijk
SQL Server MVP
"Jan" <_NO_SPAM_@.telia.com> wrote in message
news:OUgXrrU8DHA.2316@.TK2MSFTNGP09.phx.gbl...
> F.Y.I the sql server i configure:
> Dynamically configure SQL server memory
> Minimum 41 MB
> Maximum 388 MB
> Minimum query memory (KB) 1024
> Jan wrote:
> > I have problem with the RAM.
> > The server is allocating 560 Mb of 512 Mb, and using the swap file.
> >
> > Is the any recomendation of memory alocating in SQL server 2000 ?
> >
> > //Jan
> >
> > Jacco Schalkwijk wrote:
> >> Considering that your database and number of users is within the
> >> limitations for MSDE (2GB data, 5 concurrent users), and MSDE is
> >> designed to run on a desktop machine, I would say that your server
> >> might be overspec'd rather than underspec'd.
> >>
> >> Do you have any performance issues with it?
> >>
> >>
> >> "Jan" <_NO_SPAM_@.telia.com> wrote in message
> >> news:O2LAncL8DHA.1548@.tk2msftngp13.phx.gbl...
> >> Hi !
> >>
> >> We have a sql server 2000, IIS and windows 2000 op-sys.
> >> 1133 Mhz cpu, 512 Mb RAM, raid5 scsi disk.
> >>
> >> One prod database size 1164 Mb
> >> Two test databases size 45 Mb
> >>
> >> The server have 4 user in production and 1 programmer.
> >>
> >> Is this server to small ?
> >> If yes, what should we upgrade ?
> >>
> >> Regards Jan Rockstedt
>
>
Showing posts with label disk. Show all posts
Showing posts with label disk. Show all posts
Monday, March 12, 2012
Friday, March 9, 2012
Hardware Failure Of Disk Drive
Hello,
While researching potential solutions to expand the disk capacity of our
server I have come across a question that I hope someone in here is able to
answer.
For example a database has got 4 file groups, each with critical data on all
of them. These are directly connected to the server either by internal RAID
config or SAN device. While the database is in operation a transaction is
opened across all file groups, updating and inserting data to all 4. During
this process a RAID card or connection to the SAN fails cutting the
connection to file groups 3 and 4.
The transaction being execured then hits an error (as it cannot continue to
update and read 3 and 4) and goes to rollback transaction. The rollback
however is successful on the file groups 1 and 2 but not on 3 and 4. Thus
potentially leaving data inconsistency.
Am I correct in assuming this? If so, is there any way to combat this
possible situation. Though, I do understand that the likelyhood of a RAID
card or SAN failing is remote the chance is still there.
Thanks
Anubis.If a write fails under these conditions then the database will certainly be
marked Suspect at which point a restore from backup is going to be your best
option. Regular transaction log backups are the simplest way to mitigate
this. Log shipping is an additional option.
On the hardware side, it's possible to mirror over redundant controllers for
RAID or use multiple controllers with failover in a SAN, which will prevent
or limit data loss and downtime in the event of a disk or controller
failure.
David Portas
SQL Server MVP
--|||My understanding is that if it's not committed when the DB restarts it
should rollback the remaining file group 3 and 4 when their connectivity is
back.|||Hello,
This was my understanding also, though, if a database looses connectivity to
a file group would it stop accepting or working with the other files and go
'offline' or does it continue to work with the other files?
"Peter Yao" <peteryao@.NoSPAMhotmail.com> wrote in message
news:%23AR8ACHcFHA.3280@.TK2MSFTNGP09.phx.gbl...
> My understanding is that if it's not committed when the DB restarts it
> should rollback the remaining file group 3 and 4 when their connectivity
> is
> back.
>
While researching potential solutions to expand the disk capacity of our
server I have come across a question that I hope someone in here is able to
answer.
For example a database has got 4 file groups, each with critical data on all
of them. These are directly connected to the server either by internal RAID
config or SAN device. While the database is in operation a transaction is
opened across all file groups, updating and inserting data to all 4. During
this process a RAID card or connection to the SAN fails cutting the
connection to file groups 3 and 4.
The transaction being execured then hits an error (as it cannot continue to
update and read 3 and 4) and goes to rollback transaction. The rollback
however is successful on the file groups 1 and 2 but not on 3 and 4. Thus
potentially leaving data inconsistency.
Am I correct in assuming this? If so, is there any way to combat this
possible situation. Though, I do understand that the likelyhood of a RAID
card or SAN failing is remote the chance is still there.
Thanks
Anubis.If a write fails under these conditions then the database will certainly be
marked Suspect at which point a restore from backup is going to be your best
option. Regular transaction log backups are the simplest way to mitigate
this. Log shipping is an additional option.
On the hardware side, it's possible to mirror over redundant controllers for
RAID or use multiple controllers with failover in a SAN, which will prevent
or limit data loss and downtime in the event of a disk or controller
failure.
David Portas
SQL Server MVP
--|||My understanding is that if it's not committed when the DB restarts it
should rollback the remaining file group 3 and 4 when their connectivity is
back.|||Hello,
This was my understanding also, though, if a database looses connectivity to
a file group would it stop accepting or working with the other files and go
'offline' or does it continue to work with the other files?
"Peter Yao" <peteryao@.NoSPAMhotmail.com> wrote in message
news:%23AR8ACHcFHA.3280@.TK2MSFTNGP09.phx.gbl...
> My understanding is that if it's not committed when the DB restarts it
> should rollback the remaining file group 3 and 4 when their connectivity
> is
> back.
>
Hardware Failure Of Disk Drive
Hello,
While researching potential solutions to expand the disk capacity of our
server I have come across a question that I hope someone in here is able to
answer.
For example a database has got 4 file groups, each with critical data on all
of them. These are directly connected to the server either by internal RAID
config or SAN device. While the database is in operation a transaction is
opened across all file groups, updating and inserting data to all 4. During
this process a RAID card or connection to the SAN fails cutting the
connection to file groups 3 and 4.
The transaction being execured then hits an error (as it cannot continue to
update and read 3 and 4) and goes to rollback transaction. The rollback
however is successful on the file groups 1 and 2 but not on 3 and 4. Thus
potentially leaving data inconsistency.
Am I correct in assuming this? If so, is there any way to combat this
possible situation. Though, I do understand that the likelyhood of a RAID
card or SAN failing is remote the chance is still there.
Thanks
Anubis.
If a write fails under these conditions then the database will certainly be
marked Suspect at which point a restore from backup is going to be your best
option. Regular transaction log backups are the simplest way to mitigate
this. Log shipping is an additional option.
On the hardware side, it's possible to mirror over redundant controllers for
RAID or use multiple controllers with failover in a SAN, which will prevent
or limit data loss and downtime in the event of a disk or controller
failure.
David Portas
SQL Server MVP
|||My understanding is that if it's not committed when the DB restarts it
should rollback the remaining file group 3 and 4 when their connectivity is
back.
|||Hello,
This was my understanding also, though, if a database looses connectivity to
a file group would it stop accepting or working with the other files and go
'offline' or does it continue to work with the other files?
"Peter Yao" <peteryao@.NoSPAMhotmail.com> wrote in message
news:%23AR8ACHcFHA.3280@.TK2MSFTNGP09.phx.gbl...
> My understanding is that if it's not committed when the DB restarts it
> should rollback the remaining file group 3 and 4 when their connectivity
> is
> back.
>
While researching potential solutions to expand the disk capacity of our
server I have come across a question that I hope someone in here is able to
answer.
For example a database has got 4 file groups, each with critical data on all
of them. These are directly connected to the server either by internal RAID
config or SAN device. While the database is in operation a transaction is
opened across all file groups, updating and inserting data to all 4. During
this process a RAID card or connection to the SAN fails cutting the
connection to file groups 3 and 4.
The transaction being execured then hits an error (as it cannot continue to
update and read 3 and 4) and goes to rollback transaction. The rollback
however is successful on the file groups 1 and 2 but not on 3 and 4. Thus
potentially leaving data inconsistency.
Am I correct in assuming this? If so, is there any way to combat this
possible situation. Though, I do understand that the likelyhood of a RAID
card or SAN failing is remote the chance is still there.
Thanks
Anubis.
If a write fails under these conditions then the database will certainly be
marked Suspect at which point a restore from backup is going to be your best
option. Regular transaction log backups are the simplest way to mitigate
this. Log shipping is an additional option.
On the hardware side, it's possible to mirror over redundant controllers for
RAID or use multiple controllers with failover in a SAN, which will prevent
or limit data loss and downtime in the event of a disk or controller
failure.
David Portas
SQL Server MVP
|||My understanding is that if it's not committed when the DB restarts it
should rollback the remaining file group 3 and 4 when their connectivity is
back.
|||Hello,
This was my understanding also, though, if a database looses connectivity to
a file group would it stop accepting or working with the other files and go
'offline' or does it continue to work with the other files?
"Peter Yao" <peteryao@.NoSPAMhotmail.com> wrote in message
news:%23AR8ACHcFHA.3280@.TK2MSFTNGP09.phx.gbl...
> My understanding is that if it's not committed when the DB restarts it
> should rollback the remaining file group 3 and 4 when their connectivity
> is
> back.
>
Hardware Failure Of Disk Drive
Hello,
While researching potential solutions to expand the disk capacity of our
server I have come across a question that I hope someone in here is able to
answer.
For example a database has got 4 file groups, each with critical data on all
of them. These are directly connected to the server either by internal RAID
config or SAN device. While the database is in operation a transaction is
opened across all file groups, updating and inserting data to all 4. During
this process a RAID card or connection to the SAN fails cutting the
connection to file groups 3 and 4.
The transaction being execured then hits an error (as it cannot continue to
update and read 3 and 4) and goes to rollback transaction. The rollback
however is successful on the file groups 1 and 2 but not on 3 and 4. Thus
potentially leaving data inconsistency.
Am I correct in assuming this? If so, is there any way to combat this
possible situation. Though, I do understand that the likelyhood of a RAID
card or SAN failing is remote the chance is still there.
Thanks
Anubis.If a write fails under these conditions then the database will certainly be
marked Suspect at which point a restore from backup is going to be your best
option. Regular transaction log backups are the simplest way to mitigate
this. Log shipping is an additional option.
On the hardware side, it's possible to mirror over redundant controllers for
RAID or use multiple controllers with failover in a SAN, which will prevent
or limit data loss and downtime in the event of a disk or controller
failure.
--
David Portas
SQL Server MVP
--|||My understanding is that if it's not committed when the DB restarts it
should rollback the remaining file group 3 and 4 when their connectivity is
back.|||Hello,
This was my understanding also, though, if a database looses connectivity to
a file group would it stop accepting or working with the other files and go
'offline' or does it continue to work with the other files?
"Peter Yao" <peteryao@.NoSPAMhotmail.com> wrote in message
news:%23AR8ACHcFHA.3280@.TK2MSFTNGP09.phx.gbl...
> My understanding is that if it's not committed when the DB restarts it
> should rollback the remaining file group 3 and 4 when their connectivity
> is
> back.
>
While researching potential solutions to expand the disk capacity of our
server I have come across a question that I hope someone in here is able to
answer.
For example a database has got 4 file groups, each with critical data on all
of them. These are directly connected to the server either by internal RAID
config or SAN device. While the database is in operation a transaction is
opened across all file groups, updating and inserting data to all 4. During
this process a RAID card or connection to the SAN fails cutting the
connection to file groups 3 and 4.
The transaction being execured then hits an error (as it cannot continue to
update and read 3 and 4) and goes to rollback transaction. The rollback
however is successful on the file groups 1 and 2 but not on 3 and 4. Thus
potentially leaving data inconsistency.
Am I correct in assuming this? If so, is there any way to combat this
possible situation. Though, I do understand that the likelyhood of a RAID
card or SAN failing is remote the chance is still there.
Thanks
Anubis.If a write fails under these conditions then the database will certainly be
marked Suspect at which point a restore from backup is going to be your best
option. Regular transaction log backups are the simplest way to mitigate
this. Log shipping is an additional option.
On the hardware side, it's possible to mirror over redundant controllers for
RAID or use multiple controllers with failover in a SAN, which will prevent
or limit data loss and downtime in the event of a disk or controller
failure.
--
David Portas
SQL Server MVP
--|||My understanding is that if it's not committed when the DB restarts it
should rollback the remaining file group 3 and 4 when their connectivity is
back.|||Hello,
This was my understanding also, though, if a database looses connectivity to
a file group would it stop accepting or working with the other files and go
'offline' or does it continue to work with the other files?
"Peter Yao" <peteryao@.NoSPAMhotmail.com> wrote in message
news:%23AR8ACHcFHA.3280@.TK2MSFTNGP09.phx.gbl...
> My understanding is that if it's not committed when the DB restarts it
> should rollback the remaining file group 3 and 4 when their connectivity
> is
> back.
>
Wednesday, March 7, 2012
Hard Drive Space and Disk Caching
Dear friends
I have what may be a basic question to most folks here. Does SQL manage disk caching across partitions or hard drives for greatest efficiency
Basically I have a small C drive partition reserved for basic operating systems stuff. All program and data files, including SQL and databases are on the much larger D and E drives. Would there ever be an issue of the C drive not being large enough and causing SQL to slow down or not perform as well
Someone told me that all disk caching happens on the C drive, which doesn't make sense to me. It seems to me that SQL would be smart enough to use other physical drive resources as needed. They are encouraging us to use Partition Magic to expand the size of our C drive (which currently has about 1 Gig available, to be expanded to between 5 and 10 Gig)
Does this seem like good advice?I do not understand what they are saying - by definition caching is =holding data locally for fast access, SQL Server holds data in memory =having read it from disc. What drive letter is utterly irrelevant to it =(and from a data management perspective the whole concept of drive =letters is horrid!)
SQL Server caching is fine across any drive letter - it cares little =about such things. I have one system where C is getting really tight =(due to successive service packs and fixes) but all the SQL server =stuff, pagefile etc is elsewhere and we have noticed no performance =problems.
Mike John
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message =news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
> > I have what may be a basic question to most folks here. Does SQL =manage disk caching across partitions or hard drives for greatest =efficiency?
> > Basically I have a small C drive partition reserved for basic =operating systems stuff. All program and data files, including SQL and =databases are on the much larger D and E drives. Would there ever be an =issue of the C drive not being large enough and causing SQL to slow down =or not perform as well?
> > Someone told me that all disk caching happens on the C drive, which =doesn't make sense to me. It seems to me that SQL would be smart enough =to use other physical drive resources as needed. They are encouraging =us to use Partition Magic to expand the size of our C drive (which =currently has about 1 Gig available, to be expanded to between 5 and 10 =Gig).
> > Does this seem like good advice?|||Kevin,
First off sql servers cache is a memory based cache not a disk one. The
cache your thinking of is the OS cache or virtual memory. A properly tuned
Sql Server will not use this cache at all. And yes it is usually on the c:
drive. Second it sounds like your drives are all logical drives on the same
physical hard drive. If this is the case it doesn't matter since it is all
the same physical drive. Having multiple logical partitions is more of a
hindrance than a help in that case.
--
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
> I have what may be a basic question to most folks here. Does SQL manage
disk caching across partitions or hard drives for greatest efficiency?
> Basically I have a small C drive partition reserved for basic operating
systems stuff. All program and data files, including SQL and databases are
on the much larger D and E drives. Would there ever be an issue of the C
drive not being large enough and causing SQL to slow down or not perform as
well?
> Someone told me that all disk caching happens on the C drive, which
doesn't make sense to me. It seems to me that SQL would be smart enough to
use other physical drive resources as needed. They are encouraging us to
use Partition Magic to expand the size of our C drive (which currently has
about 1 Gig available, to be expanded to between 5 and 10 Gig).
> Does this seem like good advice?|||Dear Andriew and Mike,
Thank you both for your responses. It seems to me, from them, that we do not have an immediate need to re-partition our hard drive.
I did wonder what you had in mind Andrew, though, when you said:
"Having multiple logical partitions is more of a hindrance than a help in that case."
Pardon my naivete. Thanks!
In Peace,
K.|||Two things that I see often. One is that by having several logical drives
it tends to give the impression there are multiple physical drives. For
someone not familiar with the hardware they may make assumptions that are
wrong based on this. The other is that by having multiple logical
partitions you effectively limit how much space you have in each. Where as
if it was all one logical partition you don't have to worry about running
out of room until you hit the disk limit, not the partition limit. Hope
that helps.
--
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:41D04118-B9C2-45BD-8D81-1179187976F6@.microsoft.com...
> Dear Andriew and Mike,
> Thank you both for your responses. It seems to me, from them, that we do
not have an immediate need to re-partition our hard drive.
> I did wonder what you had in mind Andrew, though, when you said:
> "Having multiple logical partitions is more of a hindrance than a help in
that case."
> Pardon my naivete. Thanks!
> In Peace,
> K.
>
I have what may be a basic question to most folks here. Does SQL manage disk caching across partitions or hard drives for greatest efficiency
Basically I have a small C drive partition reserved for basic operating systems stuff. All program and data files, including SQL and databases are on the much larger D and E drives. Would there ever be an issue of the C drive not being large enough and causing SQL to slow down or not perform as well
Someone told me that all disk caching happens on the C drive, which doesn't make sense to me. It seems to me that SQL would be smart enough to use other physical drive resources as needed. They are encouraging us to use Partition Magic to expand the size of our C drive (which currently has about 1 Gig available, to be expanded to between 5 and 10 Gig)
Does this seem like good advice?I do not understand what they are saying - by definition caching is =holding data locally for fast access, SQL Server holds data in memory =having read it from disc. What drive letter is utterly irrelevant to it =(and from a data management perspective the whole concept of drive =letters is horrid!)
SQL Server caching is fine across any drive letter - it cares little =about such things. I have one system where C is getting really tight =(due to successive service packs and fixes) but all the SQL server =stuff, pagefile etc is elsewhere and we have noticed no performance =problems.
Mike John
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message =news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
> > I have what may be a basic question to most folks here. Does SQL =manage disk caching across partitions or hard drives for greatest =efficiency?
> > Basically I have a small C drive partition reserved for basic =operating systems stuff. All program and data files, including SQL and =databases are on the much larger D and E drives. Would there ever be an =issue of the C drive not being large enough and causing SQL to slow down =or not perform as well?
> > Someone told me that all disk caching happens on the C drive, which =doesn't make sense to me. It seems to me that SQL would be smart enough =to use other physical drive resources as needed. They are encouraging =us to use Partition Magic to expand the size of our C drive (which =currently has about 1 Gig available, to be expanded to between 5 and 10 =Gig).
> > Does this seem like good advice?|||Kevin,
First off sql servers cache is a memory based cache not a disk one. The
cache your thinking of is the OS cache or virtual memory. A properly tuned
Sql Server will not use this cache at all. And yes it is usually on the c:
drive. Second it sounds like your drives are all logical drives on the same
physical hard drive. If this is the case it doesn't matter since it is all
the same physical drive. Having multiple logical partitions is more of a
hindrance than a help in that case.
--
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
> I have what may be a basic question to most folks here. Does SQL manage
disk caching across partitions or hard drives for greatest efficiency?
> Basically I have a small C drive partition reserved for basic operating
systems stuff. All program and data files, including SQL and databases are
on the much larger D and E drives. Would there ever be an issue of the C
drive not being large enough and causing SQL to slow down or not perform as
well?
> Someone told me that all disk caching happens on the C drive, which
doesn't make sense to me. It seems to me that SQL would be smart enough to
use other physical drive resources as needed. They are encouraging us to
use Partition Magic to expand the size of our C drive (which currently has
about 1 Gig available, to be expanded to between 5 and 10 Gig).
> Does this seem like good advice?|||Dear Andriew and Mike,
Thank you both for your responses. It seems to me, from them, that we do not have an immediate need to re-partition our hard drive.
I did wonder what you had in mind Andrew, though, when you said:
"Having multiple logical partitions is more of a hindrance than a help in that case."
Pardon my naivete. Thanks!
In Peace,
K.|||Two things that I see often. One is that by having several logical drives
it tends to give the impression there are multiple physical drives. For
someone not familiar with the hardware they may make assumptions that are
wrong based on this. The other is that by having multiple logical
partitions you effectively limit how much space you have in each. Where as
if it was all one logical partition you don't have to worry about running
out of room until you hit the disk limit, not the partition limit. Hope
that helps.
--
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:41D04118-B9C2-45BD-8D81-1179187976F6@.microsoft.com...
> Dear Andriew and Mike,
> Thank you both for your responses. It seems to me, from them, that we do
not have an immediate need to re-partition our hard drive.
> I did wonder what you had in mind Andrew, though, when you said:
> "Having multiple logical partitions is more of a hindrance than a help in
that case."
> Pardon my naivete. Thanks!
> In Peace,
> K.
>
Hard Drive Space and Disk Caching
Dear friends,
I have what may be a basic question to most folks here. Does SQL manage dis
k caching across partitions or hard drives for greatest efficiency?
Basically I have a small C drive partition reserved for basic operating syst
ems stuff. All program and data files, including SQL and databases are on t
he much larger D and E drives. Would there ever be an issue of the C drive
not being large enough and
causing SQL to slow down or not perform as well?
Someone told me that all disk caching happens on the C drive, which doesn't
make sense to me. It seems to me that SQL would be smart enough to use othe
r physical drive resources as needed. They are encouraging us to use Partit
ion Magic to expand the siz
e of our C drive (which currently has about 1 Gig available, to be expanded
to between 5 and 10 Gig).
Does this seem like good advice?I do not understand what they are saying - by definition caching is =
holding data locally for fast access, SQL Server holds data in memory =
having read it from disc. What drive letter is utterly irrelevant to it =
(and from a data management perspective the whole concept of drive =
letters is horrid!)=20
SQL Server caching is fine across any drive letter - it cares little =
about such things. I have one system where C is getting really tight =
(due to successive service packs and fixes) but all the SQL server =
stuff, pagefile etc is elsewhere and we have noticed no performance =
problems.
Mike John
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message =
news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
>=20
> I have what may be a basic question to most folks here. Does SQL =
manage disk caching across partitions or hard drives for greatest =
efficiency?
>=20
> Basically I have a small C drive partition reserved for basic =
operating systems stuff. All program and data files, including SQL and =
databases are on the much larger D and E drives. Would there ever be an =
issue of the C drive not being large enough and causing SQL to slow down =
or not perform as well?
>=20
> Someone told me that all disk caching happens on the C drive, which =
doesn't make sense to me. It seems to me that SQL would be smart enough =
to use other physical drive resources as needed. They are encouraging =
us to use Partition Magic to expand the size of our C drive (which =
currently has about 1 Gig available, to be expanded to between 5 and 10 =
Gig).
>=20
> Does this seem like good advice?|||Kevin,
First off sql servers cache is a memory based cache not a disk one. The
cache your thinking of is the OS cache or virtual memory. A properly tuned
Sql Server will not use this cache at all. And yes it is usually on the c:
drive. Second it sounds like your drives are all logical drives on the same
physical hard drive. If this is the case it doesn't matter since it is all
the same physical drive. Having multiple logical partitions is more of a
hindrance than a help in that case.
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
> I have what may be a basic question to most folks here. Does SQL manage
disk caching across partitions or hard drives for greatest efficiency?
> Basically I have a small C drive partition reserved for basic operating
systems stuff. All program and data files, including SQL and databases are
on the much larger D and E drives. Would there ever be an issue of the C
drive not being large enough and causing SQL to slow down or not perform as
well?
> Someone told me that all disk caching happens on the C drive, which
doesn't make sense to me. It seems to me that SQL would be smart enough to
use other physical drive resources as needed. They are encouraging us to
use Partition Magic to expand the size of our C drive (which currently has
about 1 Gig available, to be expanded to between 5 and 10 Gig).
> Does this seem like good advice?|||Dear Andriew and Mike,
Thank you both for your responses. It seems to me, from them, that we do no
t have an immediate need to re-partition our hard drive.
I did wonder what you had in mind Andrew, though, when you said:
"Having multiple logical partitions is more of a hindrance than a help in th
at case."
Pardon my naivete. Thanks!
In Peace,
K.|||Two things that I see often. One is that by having several logical drives
it tends to give the impression there are multiple physical drives. For
someone not familiar with the hardware they may make assumptions that are
wrong based on this. The other is that by having multiple logical
partitions you effectively limit how much space you have in each. Where as
if it was all one logical partition you don't have to worry about running
out of room until you hit the disk limit, not the partition limit. Hope
that helps.
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:41D04118-B9C2-45BD-8D81-1179187976F6@.microsoft.com...
> Dear Andriew and Mike,
> Thank you both for your responses. It seems to me, from them, that we do
not have an immediate need to re-partition our hard drive.
> I did wonder what you had in mind Andrew, though, when you said:
> "Having multiple logical partitions is more of a hindrance than a help in
that case."
> Pardon my naivete. Thanks!
> In Peace,
> K.
>
I have what may be a basic question to most folks here. Does SQL manage dis
k caching across partitions or hard drives for greatest efficiency?
Basically I have a small C drive partition reserved for basic operating syst
ems stuff. All program and data files, including SQL and databases are on t
he much larger D and E drives. Would there ever be an issue of the C drive
not being large enough and
causing SQL to slow down or not perform as well?
Someone told me that all disk caching happens on the C drive, which doesn't
make sense to me. It seems to me that SQL would be smart enough to use othe
r physical drive resources as needed. They are encouraging us to use Partit
ion Magic to expand the siz
e of our C drive (which currently has about 1 Gig available, to be expanded
to between 5 and 10 Gig).
Does this seem like good advice?I do not understand what they are saying - by definition caching is =
holding data locally for fast access, SQL Server holds data in memory =
having read it from disc. What drive letter is utterly irrelevant to it =
(and from a data management perspective the whole concept of drive =
letters is horrid!)=20
SQL Server caching is fine across any drive letter - it cares little =
about such things. I have one system where C is getting really tight =
(due to successive service packs and fixes) but all the SQL server =
stuff, pagefile etc is elsewhere and we have noticed no performance =
problems.
Mike John
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message =
news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
>=20
> I have what may be a basic question to most folks here. Does SQL =
manage disk caching across partitions or hard drives for greatest =
efficiency?
>=20
> Basically I have a small C drive partition reserved for basic =
operating systems stuff. All program and data files, including SQL and =
databases are on the much larger D and E drives. Would there ever be an =
issue of the C drive not being large enough and causing SQL to slow down =
or not perform as well?
>=20
> Someone told me that all disk caching happens on the C drive, which =
doesn't make sense to me. It seems to me that SQL would be smart enough =
to use other physical drive resources as needed. They are encouraging =
us to use Partition Magic to expand the size of our C drive (which =
currently has about 1 Gig available, to be expanded to between 5 and 10 =
Gig).
>=20
> Does this seem like good advice?|||Kevin,
First off sql servers cache is a memory based cache not a disk one. The
cache your thinking of is the OS cache or virtual memory. A properly tuned
Sql Server will not use this cache at all. And yes it is usually on the c:
drive. Second it sounds like your drives are all logical drives on the same
physical hard drive. If this is the case it doesn't matter since it is all
the same physical drive. Having multiple logical partitions is more of a
hindrance than a help in that case.
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:4376A82B-AC21-463C-BCDD-B124FE980C98@.microsoft.com...
> Dear friends,
> I have what may be a basic question to most folks here. Does SQL manage
disk caching across partitions or hard drives for greatest efficiency?
> Basically I have a small C drive partition reserved for basic operating
systems stuff. All program and data files, including SQL and databases are
on the much larger D and E drives. Would there ever be an issue of the C
drive not being large enough and causing SQL to slow down or not perform as
well?
> Someone told me that all disk caching happens on the C drive, which
doesn't make sense to me. It seems to me that SQL would be smart enough to
use other physical drive resources as needed. They are encouraging us to
use Partition Magic to expand the size of our C drive (which currently has
about 1 Gig available, to be expanded to between 5 and 10 Gig).
> Does this seem like good advice?|||Dear Andriew and Mike,
Thank you both for your responses. It seems to me, from them, that we do no
t have an immediate need to re-partition our hard drive.
I did wonder what you had in mind Andrew, though, when you said:
"Having multiple logical partitions is more of a hindrance than a help in th
at case."
Pardon my naivete. Thanks!
In Peace,
K.|||Two things that I see often. One is that by having several logical drives
it tends to give the impression there are multiple physical drives. For
someone not familiar with the hardware they may make assumptions that are
wrong based on this. The other is that by having multiple logical
partitions you effectively limit how much space you have in each. Where as
if it was all one logical partition you don't have to worry about running
out of room until you hit the disk limit, not the partition limit. Hope
that helps.
Andrew J. Kelly
SQL Server MVP
"Kevin" <anonymous@.discussions.microsoft.com> wrote in message
news:41D04118-B9C2-45BD-8D81-1179187976F6@.microsoft.com...
> Dear Andriew and Mike,
> Thank you both for your responses. It seems to me, from them, that we do
not have an immediate need to re-partition our hard drive.
> I did wonder what you had in mind Andrew, though, when you said:
> "Having multiple logical partitions is more of a hindrance than a help in
that case."
> Pardon my naivete. Thanks!
> In Peace,
> K.
>
Hard disk configuration question
I just acquire a new server with 8 hard drives and 2 RAID controllers. The
objective is to load SQL SERVER 2005 on this server to run CRM and one other
database centric application. In addition rerporting services and analysis
services will also be installed. I have configured two of the RAID hard
disks as RAID1 and created the System partition on it as Drive C (30GB) and
the remaining as Drive D.
I configured another 2 as RAID1 (67GB) which I intend to use for the
Databases log files.
I now have 4 hard disks left. I can either configure this drives as 1 RAID5
Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an issue
here, I am trying to achieve the best possible performance. Which RAID
configuration is better for the data files? Any suggestions or
recommendations?
Thank you,
ODMake the 4 hard drives RAID 10 (mirror then striping).
Don't even touch RAID 5 with a barge poll now-a-days.
Put tempdb on the D: on its own RAID 1 array away from the second and third
arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
recommending it has its own uncontended array and even use a RAM disk if a)
the RAM disk fully supports SQL Server IO requirements and b) you have spare
memory in the box and c) if your application pattern after testing benefits
that approach (which stuff with heaving sorting, hashing, temp table usage
will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short lived # tables -
do they get written to disk?
(http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||With 8 drives, my suggestion for best performance is:
Two Drives -RAID 1 (log files)
Three Drives RAID 0
Three Drives RAID 0
Mirror the above two RAID 0 sets, making a RAID 10.
Use the RAID 10 for OS and datafiles.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||Thats RAID 01 which isn't as fault tolerant as RAID 10.
01 is striping and then mirroring the stripe; if a disk in the stripe fails
then your whole array is exposed and a single drive failure on the second
mirrored striped can cause the set to be unavailable.
10 is mirror the drives and then stripe across, if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for the
one that failed then you are ok.
Basically, you can lose more drives RAID 10 then with RAID 01.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
> With 8 drives, my suggestion for best performance is:
> Two Drives -RAID 1 (log files)
> Three Drives RAID 0
> Three Drives RAID 0
> Mirror the above two RAID 0 sets, making a RAID 10.
> Use the RAID 10 for OS and datafiles.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>>objective is to load SQL SERVER 2005 on this server to run CRM and one
>>other database centric application. In addition rerporting services and
>>analysis services will also be installed. I have configured two of the
>>RAID hard disks as RAID1 and created the System partition on it as Drive C
>>(30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
>> issue here, I am trying to achieve the best possible performance. Which
>> RAID configuration is better for the data files? Any suggestions or
>> recommendations?
>> Thank you,
>> OD
>|||Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
locate the Data files for Tempdb on the RAID 10 set with other user create
data files?
here is what I will have:
-RAID 1: partitioned to DRIVE C (for System) and D (May be backup and other
media files).
-RAID 1: Partioned to E (for logs) and F: for backup
-RAID 10: Partioned to G and H for different data files
what do you think?
OD
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
> Make the 4 hard drives RAID 10 (mirror then striping).
> Don't even touch RAID 5 with a barge poll now-a-days.
> Put tempdb on the D: on its own RAID 1 array away from the second and
> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
> recommending it has its own uncontended array and even use a RAM disk if
> a) the RAM disk fully supports SQL Server IO requirements and b) you have
> spare memory in the box and c) if your application pattern after testing
> benefits that approach (which stuff with heaving sorting, hashing, temp
> table usage will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short
> lived # tables - do they get written to disk?
> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>>objective is to load SQL SERVER 2005 on this server to run CRM and one
>>other database centric application. In addition rerporting services and
>>analysis services will also be installed. I have configured two of the
>>RAID hard disks as RAID1 and created the System partition on it as Drive C
>>(30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
>> issue here, I am trying to achieve the best possible performance. Which
>> RAID configuration is better for the data files? Any suggestions or
>> recommendations?
>> Thank you,
>> OD
>|||Hi OD,
> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
> other user create data files?
Why? Your system should rarely ever page so disk performance to the RAID 1
array containing pagefile.sys should not be a problem - better to utilise
it, if your box is paging (thereby causing IO to that RAID 1 array) then you
have other memory problems to solve first anyway, by using D: you aren't
touching the logical system drive so you will have enough space to put the
pagefile.sys (fix this rather than allow OS to grow it).
Think of tempdb in the same way you think of a database transaction log.
Why have RAID 10 partitioned as G and H? Just make it one logical drive -
drive G:
Again, why partition RAID 1 as E: and F: - just make it one logical drive -
drive E:
When you format the partitions in NT, format them NTFS but give it an
allocation size that matches your RAID stripe size, its usually 64K.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
> Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
> they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
> locate the Data files for Tempdb on the RAID 10 set with other user create
> data files?
> here is what I will have:
> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
> other media files).
> -RAID 1: Partioned to E (for logs) and F: for backup
> -RAID 10: Partioned to G and H for different data files
> what do you think?
> OD
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM disk
>> if a) the RAM disk fully supports SQL Server IO requirements and b) you
>> have spare memory in the box and c) if your application pattern after
>> testing benefits that approach (which stuff with heaving sorting,
>> hashing, temp table usage will) - see my blog entry: Put TEMPDB on a RAM
>> DRIVE; Short lived # tables - do they get written to disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>|||Thanks Tony, for the additional information.
However, as I was apt to do in my many Econ classes, I love to challenge the
assumptions. Anytime there is an 'IF', as in:
"if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for
the
one that failed then you are ok"
It seems mirrored stripes AND stripped mirrors are both vulnerable to
multiple drive failures. However, as you indicated, the stripped mirrors
seem to provide a little bit more of a element of chance to which mirrored
drive fails, whereas with mirrored stripes, failure in the mirror is certain
'death'.
One could posit that all of society survives on the element of chance.
Another day, another useful bit of information gleaned.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
> Thats RAID 01 which isn't as fault tolerant as RAID 10.
> 01 is striping and then mirroring the stripe; if a disk in the stripe
> fails then your whole array is exposed and a single drive failure on the
> second mirrored striped can cause the set to be unavailable.
> 10 is mirror the drives and then stripe across, if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for the
> one that failed then you are ok.
> Basically, you can lose more drives RAID 10 then with RAID 01.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>> With 8 drives, my suggestion for best performance is:
>> Two Drives -RAID 1 (log files)
>> Three Drives RAID 0
>> Three Drives RAID 0
>> Mirror the above two RAID 0 sets, making a RAID 10.
>> Use the RAID 10 for OS and datafiles.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>|||Thank you all for the assistance. In that case, I will stick with your
earlier advice as so:
First RAID 1
--C: ->System and Binary
--D: -> TempDB
Second Raid 1
--E: -> LOGS + Backup
RAID 10
--F: Data files
Now that the DB spaces have been figured out will it be ok (performance
wise) for one of Drives D, E or F to also hold other data such as Word and
Excel files that are generated by one of the appliations?
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
> Hi OD,
>> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
>> other user create data files?
> Why? Your system should rarely ever page so disk performance to the RAID 1
> array containing pagefile.sys should not be a problem - better to utilise
> it, if your box is paging (thereby causing IO to that RAID 1 array) then
> you have other memory problems to solve first anyway, by using D: you
> aren't touching the logical system drive so you will have enough space to
> put the pagefile.sys (fix this rather than allow OS to grow it).
> Think of tempdb in the same way you think of a database transaction log.
> Why have RAID 10 partitioned as G and H? Just make it one logical drive -
> drive G:
> Again, why partition RAID 1 as E: and F: - just make it one logical
> drive - drive E:
> When you format the partitions in NT, format them NTFS but give it an
> allocation size that matches your RAID stripe size, its usually 64K.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>> Thanks for the recomendation. Drive C and D are on the same RAID 1 set
>> but they are 2 different OS partition on the RAID Vitual Disk. Is it ok
>> to locate the Data files for Tempdb on the RAID 10 set with other user
>> create data files?
>> here is what I will have:
>> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
>> other media files).
>> -RAID 1: Partioned to E (for logs) and F: for backup
>> -RAID 10: Partioned to G and H for different data files
>> what do you think?
>> OD
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM
>> disk if a) the RAM disk fully supports SQL Server IO requirements and b)
>> you have spare memory in the box and c) if your application pattern
>> after testing benefits that approach (which stuff with heaving sorting,
>> hashing, temp table usage will) - see my blog entry: Put TEMPDB on a RAM
>> DRIVE; Short lived # tables - do they get written to disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>|||You raise a good point.
Something else I've seen is that all the onboard SATA RAID controllers I've
seen so far implement RAID 01, so if you want RAID 10 you must RAID 1 the
drives first and then use Windows to stripe across the drives.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>> Thats RAID 01 which isn't as fault tolerant as RAID 10.
>> 01 is striping and then mirroring the stripe; if a disk in the stripe
>> fails then your whole array is exposed and a single drive failure on the
>> second mirrored striped can cause the set to be unavailable.
>> 10 is mirror the drives and then stripe across, if a disk in the stripe
>> fails then so long as a disk in the mirror stripe isn't the mirror for
>> the one that failed then you are ok.
>> Basically, you can lose more drives RAID 10 then with RAID 01.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "Arnie Rowland" <arnie@.1568.com> wrote in message
>> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>> With 8 drives, my suggestion for best performance is:
>> Two Drives -RAID 1 (log files)
>> Three Drives RAID 0
>> Three Drives RAID 0
>> Mirror the above two RAID 0 sets, making a RAID 10.
>> Use the RAID 10 for OS and datafiles.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>|||I am running a DELL PERC 5 RAID controller and it explains this same thing.
However, it only allows configuration for RAIDs 0, 1, 5, and 10. So I have
configured the last 4 drives as RAID 10 since it's the only option supported
on the controller between RAID 01 and RAID 10.
thank you for your assistance.
OD
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>> Thats RAID 01 which isn't as fault tolerant as RAID 10.
>> 01 is striping and then mirroring the stripe; if a disk in the stripe
>> fails then your whole array is exposed and a single drive failure on the
>> second mirrored striped can cause the set to be unavailable.
>> 10 is mirror the drives and then stripe across, if a disk in the stripe
>> fails then so long as a disk in the mirror stripe isn't the mirror for
>> the one that failed then you are ok.
>> Basically, you can lose more drives RAID 10 then with RAID 01.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "Arnie Rowland" <arnie@.1568.com> wrote in message
>> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>> With 8 drives, my suggestion for best performance is:
>> Two Drives -RAID 1 (log files)
>> Three Drives RAID 0
>> Three Drives RAID 0
>> Mirror the above two RAID 0 sets, making a RAID 10.
>> Use the RAID 10 for OS and datafiles.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>|||> Now that the DB spaces have been figured out will it be ok (performance
> wise) for one of Drives D, E or F to also hold other data such as Word and
> Excel files that are generated by one of the appliations?
Depends on the volume, if you have an application that is continuously
knocking out files then I'd advise something else, but if its just a file
server then you need to ask yourself how often are files read or written
to/from and that will answer your question, I'd probably put the files on
the RAID 10 array because you really need the IO bandwidth for the
checkpoint process or when dirty pages are being written out.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:u%23XUZD4yGHA.3552@.TK2MSFTNGP02.phx.gbl...
> Thank you all for the assistance. In that case, I will stick with your
> earlier advice as so:
> First RAID 1
> --C: ->System and Binary
> --D: -> TempDB
> Second Raid 1
> --E: -> LOGS + Backup
> RAID 10
> --F: Data files
> Now that the DB spaces have been figured out will it be ok (performance
> wise) for one of Drives D, E or F to also hold other data such as Word and
> Excel files that are generated by one of the appliations?
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
>> Hi OD,
>> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
>> other user create data files?
>> Why? Your system should rarely ever page so disk performance to the RAID
>> 1 array containing pagefile.sys should not be a problem - better to
>> utilise it, if your box is paging (thereby causing IO to that RAID 1
>> array) then you have other memory problems to solve first anyway, by
>> using D: you aren't touching the logical system drive so you will have
>> enough space to put the pagefile.sys (fix this rather than allow OS to
>> grow it).
>> Think of tempdb in the same way you think of a database transaction log.
>> Why have RAID 10 partitioned as G and H? Just make it one logical drive -
>> drive G:
>> Again, why partition RAID 1 as E: and F: - just make it one logical
>> drive - drive E:
>> When you format the partitions in NT, format them NTFS but give it an
>> allocation size that matches your RAID stripe size, its usually 64K.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>> Thanks for the recomendation. Drive C and D are on the same RAID 1 set
>> but they are 2 different OS partition on the RAID Vitual Disk. Is it ok
>> to locate the Data files for Tempdb on the RAID 10 set with other user
>> create data files?
>> here is what I will have:
>> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
>> other media files).
>> -RAID 1: Partioned to E (for logs) and F: for backup
>> -RAID 10: Partioned to G and H for different data files
>> what do you think?
>> OD
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM
>> disk if a) the RAM disk fully supports SQL Server IO requirements and
>> b) you have spare memory in the box and c) if your application pattern
>> after testing benefits that approach (which stuff with heaving sorting,
>> hashing, temp table usage will) - see my blog entry: Put TEMPDB on a
>> RAM DRIVE; Short lived # tables - do they get written to disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from
>> a SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>>
>|||Thank you Annie and Tony. You have helped a lot and saved me sometime. I
will go ahead and drop the Excel and Word files on the RAID 10 temporarily
and if there is a performance issue I will add more hard drives and move
them.
Thanks again!.
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:O4VKpL4yGHA.1256@.TK2MSFTNGP04.phx.gbl...
>> Now that the DB spaces have been figured out will it be ok (performance
>> wise) for one of Drives D, E or F to also hold other data such as Word
>> and Excel files that are generated by one of the appliations?
> Depends on the volume, if you have an application that is continuously
> knocking out files then I'd advise something else, but if its just a file
> server then you need to ask yourself how often are files read or written
> to/from and that will answer your question, I'd probably put the files on
> the RAID 10 array because you really need the IO bandwidth for the
> checkpoint process or when dirty pages are being written out.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:u%23XUZD4yGHA.3552@.TK2MSFTNGP02.phx.gbl...
>> Thank you all for the assistance. In that case, I will stick with your
>> earlier advice as so:
>> First RAID 1
>> --C: ->System and Binary
>> --D: -> TempDB
>> Second Raid 1
>> --E: -> LOGS + Backup
>> RAID 10
>> --F: Data files
>> Now that the DB spaces have been figured out will it be ok (performance
>> wise) for one of Drives D, E or F to also hold other data such as Word
>> and Excel files that are generated by one of the appliations?
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
>> Hi OD,
>> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
>> other user create data files?
>> Why? Your system should rarely ever page so disk performance to the RAID
>> 1 array containing pagefile.sys should not be a problem - better to
>> utilise it, if your box is paging (thereby causing IO to that RAID 1
>> array) then you have other memory problems to solve first anyway, by
>> using D: you aren't touching the logical system drive so you will have
>> enough space to put the pagefile.sys (fix this rather than allow OS to
>> grow it).
>> Think of tempdb in the same way you think of a database transaction log.
>> Why have RAID 10 partitioned as G and H? Just make it one logical
>> drive - drive G:
>> Again, why partition RAID 1 as E: and F: - just make it one logical
>> drive - drive E:
>> When you format the partitions in NT, format them NTFS but give it an
>> allocation size that matches your RAID stripe size, its usually 64K.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>> Thanks for the recomendation. Drive C and D are on the same RAID 1 set
>> but they are 2 different OS partition on the RAID Vitual Disk. Is it ok
>> to locate the Data files for Tempdb on the RAID 10 set with other user
>> create data files?
>> here is what I will have:
>> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
>> other media files).
>> -RAID 1: Partioned to E (for logs) and F: for backup
>> -RAID 10: Partioned to G and H for different data files
>> what do you think?
>> OD
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM
>> disk if a) the RAM disk fully supports SQL Server IO requirements and
>> b) you have spare memory in the box and c) if your application pattern
>> after testing benefits that approach (which stuff with heaving
>> sorting, hashing, temp table usage will) - see my blog entry: Put
>> TEMPDB on a RAM DRIVE; Short lived # tables - do they get written to
>> disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from
>> a SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting
>>services and analysis services will also be installed. I have
>>configured two of the RAID hard disks as RAID1 and created the System
>>partition on it as Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much
>> of an issue here, I am trying to achieve the best possible
>> performance. Which RAID configuration is better for the data files?
>> Any suggestions or recommendations?
>> Thank you,
>> OD
>>
>>
>>
>>
>
objective is to load SQL SERVER 2005 on this server to run CRM and one other
database centric application. In addition rerporting services and analysis
services will also be installed. I have configured two of the RAID hard
disks as RAID1 and created the System partition on it as Drive C (30GB) and
the remaining as Drive D.
I configured another 2 as RAID1 (67GB) which I intend to use for the
Databases log files.
I now have 4 hard disks left. I can either configure this drives as 1 RAID5
Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an issue
here, I am trying to achieve the best possible performance. Which RAID
configuration is better for the data files? Any suggestions or
recommendations?
Thank you,
ODMake the 4 hard drives RAID 10 (mirror then striping).
Don't even touch RAID 5 with a barge poll now-a-days.
Put tempdb on the D: on its own RAID 1 array away from the second and third
arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
recommending it has its own uncontended array and even use a RAM disk if a)
the RAM disk fully supports SQL Server IO requirements and b) you have spare
memory in the box and c) if your application pattern after testing benefits
that approach (which stuff with heaving sorting, hashing, temp table usage
will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short lived # tables -
do they get written to disk?
(http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||With 8 drives, my suggestion for best performance is:
Two Drives -RAID 1 (log files)
Three Drives RAID 0
Three Drives RAID 0
Mirror the above two RAID 0 sets, making a RAID 10.
Use the RAID 10 for OS and datafiles.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||Thats RAID 01 which isn't as fault tolerant as RAID 10.
01 is striping and then mirroring the stripe; if a disk in the stripe fails
then your whole array is exposed and a single drive failure on the second
mirrored striped can cause the set to be unavailable.
10 is mirror the drives and then stripe across, if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for the
one that failed then you are ok.
Basically, you can lose more drives RAID 10 then with RAID 01.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
> With 8 drives, my suggestion for best performance is:
> Two Drives -RAID 1 (log files)
> Three Drives RAID 0
> Three Drives RAID 0
> Mirror the above two RAID 0 sets, making a RAID 10.
> Use the RAID 10 for OS and datafiles.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>>objective is to load SQL SERVER 2005 on this server to run CRM and one
>>other database centric application. In addition rerporting services and
>>analysis services will also be installed. I have configured two of the
>>RAID hard disks as RAID1 and created the System partition on it as Drive C
>>(30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
>> issue here, I am trying to achieve the best possible performance. Which
>> RAID configuration is better for the data files? Any suggestions or
>> recommendations?
>> Thank you,
>> OD
>|||Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
locate the Data files for Tempdb on the RAID 10 set with other user create
data files?
here is what I will have:
-RAID 1: partitioned to DRIVE C (for System) and D (May be backup and other
media files).
-RAID 1: Partioned to E (for logs) and F: for backup
-RAID 10: Partioned to G and H for different data files
what do you think?
OD
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
> Make the 4 hard drives RAID 10 (mirror then striping).
> Don't even touch RAID 5 with a barge poll now-a-days.
> Put tempdb on the D: on its own RAID 1 array away from the second and
> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
> recommending it has its own uncontended array and even use a RAM disk if
> a) the RAM disk fully supports SQL Server IO requirements and b) you have
> spare memory in the box and c) if your application pattern after testing
> benefits that approach (which stuff with heaving sorting, hashing, temp
> table usage will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short
> lived # tables - do they get written to disk?
> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>>objective is to load SQL SERVER 2005 on this server to run CRM and one
>>other database centric application. In addition rerporting services and
>>analysis services will also be installed. I have configured two of the
>>RAID hard disks as RAID1 and created the System partition on it as Drive C
>>(30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
>> issue here, I am trying to achieve the best possible performance. Which
>> RAID configuration is better for the data files? Any suggestions or
>> recommendations?
>> Thank you,
>> OD
>|||Hi OD,
> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
> other user create data files?
Why? Your system should rarely ever page so disk performance to the RAID 1
array containing pagefile.sys should not be a problem - better to utilise
it, if your box is paging (thereby causing IO to that RAID 1 array) then you
have other memory problems to solve first anyway, by using D: you aren't
touching the logical system drive so you will have enough space to put the
pagefile.sys (fix this rather than allow OS to grow it).
Think of tempdb in the same way you think of a database transaction log.
Why have RAID 10 partitioned as G and H? Just make it one logical drive -
drive G:
Again, why partition RAID 1 as E: and F: - just make it one logical drive -
drive E:
When you format the partitions in NT, format them NTFS but give it an
allocation size that matches your RAID stripe size, its usually 64K.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
> Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
> they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
> locate the Data files for Tempdb on the RAID 10 set with other user create
> data files?
> here is what I will have:
> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
> other media files).
> -RAID 1: Partioned to E (for logs) and F: for backup
> -RAID 10: Partioned to G and H for different data files
> what do you think?
> OD
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM disk
>> if a) the RAM disk fully supports SQL Server IO requirements and b) you
>> have spare memory in the box and c) if your application pattern after
>> testing benefits that approach (which stuff with heaving sorting,
>> hashing, temp table usage will) - see my blog entry: Put TEMPDB on a RAM
>> DRIVE; Short lived # tables - do they get written to disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>|||Thanks Tony, for the additional information.
However, as I was apt to do in my many Econ classes, I love to challenge the
assumptions. Anytime there is an 'IF', as in:
"if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for
the
one that failed then you are ok"
It seems mirrored stripes AND stripped mirrors are both vulnerable to
multiple drive failures. However, as you indicated, the stripped mirrors
seem to provide a little bit more of a element of chance to which mirrored
drive fails, whereas with mirrored stripes, failure in the mirror is certain
'death'.
One could posit that all of society survives on the element of chance.
Another day, another useful bit of information gleaned.
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
> Thats RAID 01 which isn't as fault tolerant as RAID 10.
> 01 is striping and then mirroring the stripe; if a disk in the stripe
> fails then your whole array is exposed and a single drive failure on the
> second mirrored striped can cause the set to be unavailable.
> 10 is mirror the drives and then stripe across, if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for the
> one that failed then you are ok.
> Basically, you can lose more drives RAID 10 then with RAID 01.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>> With 8 drives, my suggestion for best performance is:
>> Two Drives -RAID 1 (log files)
>> Three Drives RAID 0
>> Three Drives RAID 0
>> Mirror the above two RAID 0 sets, making a RAID 10.
>> Use the RAID 10 for OS and datafiles.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>|||Thank you all for the assistance. In that case, I will stick with your
earlier advice as so:
First RAID 1
--C: ->System and Binary
--D: -> TempDB
Second Raid 1
--E: -> LOGS + Backup
RAID 10
--F: Data files
Now that the DB spaces have been figured out will it be ok (performance
wise) for one of Drives D, E or F to also hold other data such as Word and
Excel files that are generated by one of the appliations?
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
> Hi OD,
>> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
>> other user create data files?
> Why? Your system should rarely ever page so disk performance to the RAID 1
> array containing pagefile.sys should not be a problem - better to utilise
> it, if your box is paging (thereby causing IO to that RAID 1 array) then
> you have other memory problems to solve first anyway, by using D: you
> aren't touching the logical system drive so you will have enough space to
> put the pagefile.sys (fix this rather than allow OS to grow it).
> Think of tempdb in the same way you think of a database transaction log.
> Why have RAID 10 partitioned as G and H? Just make it one logical drive -
> drive G:
> Again, why partition RAID 1 as E: and F: - just make it one logical
> drive - drive E:
> When you format the partitions in NT, format them NTFS but give it an
> allocation size that matches your RAID stripe size, its usually 64K.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>> Thanks for the recomendation. Drive C and D are on the same RAID 1 set
>> but they are 2 different OS partition on the RAID Vitual Disk. Is it ok
>> to locate the Data files for Tempdb on the RAID 10 set with other user
>> create data files?
>> here is what I will have:
>> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
>> other media files).
>> -RAID 1: Partioned to E (for logs) and F: for backup
>> -RAID 10: Partioned to G and H for different data files
>> what do you think?
>> OD
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM
>> disk if a) the RAM disk fully supports SQL Server IO requirements and b)
>> you have spare memory in the box and c) if your application pattern
>> after testing benefits that approach (which stuff with heaving sorting,
>> hashing, temp table usage will) - see my blog entry: Put TEMPDB on a RAM
>> DRIVE; Short lived # tables - do they get written to disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>|||You raise a good point.
Something else I've seen is that all the onboard SATA RAID controllers I've
seen so far implement RAID 01, so if you want RAID 10 you must RAID 1 the
drives first and then use Windows to stripe across the drives.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>> Thats RAID 01 which isn't as fault tolerant as RAID 10.
>> 01 is striping and then mirroring the stripe; if a disk in the stripe
>> fails then your whole array is exposed and a single drive failure on the
>> second mirrored striped can cause the set to be unavailable.
>> 10 is mirror the drives and then stripe across, if a disk in the stripe
>> fails then so long as a disk in the mirror stripe isn't the mirror for
>> the one that failed then you are ok.
>> Basically, you can lose more drives RAID 10 then with RAID 01.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "Arnie Rowland" <arnie@.1568.com> wrote in message
>> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>> With 8 drives, my suggestion for best performance is:
>> Two Drives -RAID 1 (log files)
>> Three Drives RAID 0
>> Three Drives RAID 0
>> Mirror the above two RAID 0 sets, making a RAID 10.
>> Use the RAID 10 for OS and datafiles.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>|||I am running a DELL PERC 5 RAID controller and it explains this same thing.
However, it only allows configuration for RAIDs 0, 1, 5, and 10. So I have
configured the last 4 drives as RAID 10 since it's the only option supported
on the controller between RAID 01 and RAID 10.
thank you for your assistance.
OD
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>> Thats RAID 01 which isn't as fault tolerant as RAID 10.
>> 01 is striping and then mirroring the stripe; if a disk in the stripe
>> fails then your whole array is exposed and a single drive failure on the
>> second mirrored striped can cause the set to be unavailable.
>> 10 is mirror the drives and then stripe across, if a disk in the stripe
>> fails then so long as a disk in the mirror stripe isn't the mirror for
>> the one that failed then you are ok.
>> Basically, you can lose more drives RAID 10 then with RAID 01.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "Arnie Rowland" <arnie@.1568.com> wrote in message
>> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>> With 8 drives, my suggestion for best performance is:
>> Two Drives -RAID 1 (log files)
>> Three Drives RAID 0
>> Three Drives RAID 0
>> Mirror the above two RAID 0 sets, making a RAID 10.
>> Use the RAID 10 for OS and datafiles.
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>|||> Now that the DB spaces have been figured out will it be ok (performance
> wise) for one of Drives D, E or F to also hold other data such as Word and
> Excel files that are generated by one of the appliations?
Depends on the volume, if you have an application that is continuously
knocking out files then I'd advise something else, but if its just a file
server then you need to ask yourself how often are files read or written
to/from and that will answer your question, I'd probably put the files on
the RAID 10 array because you really need the IO bandwidth for the
checkpoint process or when dirty pages are being written out.
--
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:u%23XUZD4yGHA.3552@.TK2MSFTNGP02.phx.gbl...
> Thank you all for the assistance. In that case, I will stick with your
> earlier advice as so:
> First RAID 1
> --C: ->System and Binary
> --D: -> TempDB
> Second Raid 1
> --E: -> LOGS + Backup
> RAID 10
> --F: Data files
> Now that the DB spaces have been figured out will it be ok (performance
> wise) for one of Drives D, E or F to also hold other data such as Word and
> Excel files that are generated by one of the appliations?
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
>> Hi OD,
>> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
>> other user create data files?
>> Why? Your system should rarely ever page so disk performance to the RAID
>> 1 array containing pagefile.sys should not be a problem - better to
>> utilise it, if your box is paging (thereby causing IO to that RAID 1
>> array) then you have other memory problems to solve first anyway, by
>> using D: you aren't touching the logical system drive so you will have
>> enough space to put the pagefile.sys (fix this rather than allow OS to
>> grow it).
>> Think of tempdb in the same way you think of a database transaction log.
>> Why have RAID 10 partitioned as G and H? Just make it one logical drive -
>> drive G:
>> Again, why partition RAID 1 as E: and F: - just make it one logical
>> drive - drive E:
>> When you format the partitions in NT, format them NTFS but give it an
>> allocation size that matches your RAID stripe size, its usually 64K.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>> Thanks for the recomendation. Drive C and D are on the same RAID 1 set
>> but they are 2 different OS partition on the RAID Vitual Disk. Is it ok
>> to locate the Data files for Tempdb on the RAID 10 set with other user
>> create data files?
>> here is what I will have:
>> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
>> other media files).
>> -RAID 1: Partioned to E (for logs) and F: for backup
>> -RAID 10: Partioned to G and H for different data files
>> what do you think?
>> OD
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM
>> disk if a) the RAM disk fully supports SQL Server IO requirements and
>> b) you have spare memory in the box and c) if your application pattern
>> after testing benefits that approach (which stuff with heaving sorting,
>> hashing, temp table usage will) - see my blog entry: Put TEMPDB on a
>> RAM DRIVE; Short lived # tables - do they get written to disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from
>> a SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting services
>>and analysis services will also be installed. I have configured two of
>>the RAID hard disks as RAID1 and created the System partition on it as
>>Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of
>> an issue here, I am trying to achieve the best possible performance.
>> Which RAID configuration is better for the data files? Any suggestions
>> or recommendations?
>> Thank you,
>> OD
>>
>>
>>
>|||Thank you Annie and Tony. You have helped a lot and saved me sometime. I
will go ahead and drop the Excel and Word files on the RAID 10 temporarily
and if there is a performance issue I will add more hard drives and move
them.
Thanks again!.
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:O4VKpL4yGHA.1256@.TK2MSFTNGP04.phx.gbl...
>> Now that the DB spaces have been figured out will it be ok (performance
>> wise) for one of Drives D, E or F to also hold other data such as Word
>> and Excel files that are generated by one of the appliations?
> Depends on the volume, if you have an application that is continuously
> knocking out files then I'd advise something else, but if its just a file
> server then you need to ask yourself how often are files read or written
> to/from and that will answer your question, I'd probably put the files on
> the RAID 10 array because you really need the IO bandwidth for the
> checkpoint process or when dirty pages are being written out.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:u%23XUZD4yGHA.3552@.TK2MSFTNGP02.phx.gbl...
>> Thank you all for the assistance. In that case, I will stick with your
>> earlier advice as so:
>> First RAID 1
>> --C: ->System and Binary
>> --D: -> TempDB
>> Second Raid 1
>> --E: -> LOGS + Backup
>> RAID 10
>> --F: Data files
>> Now that the DB spaces have been figured out will it be ok (performance
>> wise) for one of Drives D, E or F to also hold other data such as Word
>> and Excel files that are generated by one of the appliations?
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
>> Hi OD,
>> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
>> other user create data files?
>> Why? Your system should rarely ever page so disk performance to the RAID
>> 1 array containing pagefile.sys should not be a problem - better to
>> utilise it, if your box is paging (thereby causing IO to that RAID 1
>> array) then you have other memory problems to solve first anyway, by
>> using D: you aren't touching the logical system drive so you will have
>> enough space to put the pagefile.sys (fix this rather than allow OS to
>> grow it).
>> Think of tempdb in the same way you think of a database transaction log.
>> Why have RAID 10 partitioned as G and H? Just make it one logical
>> drive - drive G:
>> Again, why partition RAID 1 as E: and F: - just make it one logical
>> drive - drive E:
>> When you format the partitions in NT, format them NTFS but give it an
>> allocation size that matches your RAID stripe size, its usually 64K.
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
>> SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>> Thanks for the recomendation. Drive C and D are on the same RAID 1 set
>> but they are 2 different OS partition on the RAID Vitual Disk. Is it ok
>> to locate the Data files for Tempdb on the RAID 10 set with other user
>> create data files?
>> here is what I will have:
>> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
>> other media files).
>> -RAID 1: Partioned to E (for logs) and F: for backup
>> -RAID 10: Partioned to G and H for different data files
>> what do you think?
>> OD
>>
>> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
>> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>> Make the 4 hard drives RAID 10 (mirror then striping).
>> Don't even touch RAID 5 with a barge poll now-a-days.
>> Put tempdb on the D: on its own RAID 1 array away from the second and
>> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000
>> I'm recommending it has its own uncontended array and even use a RAM
>> disk if a) the RAM disk fully supports SQL Server IO requirements and
>> b) you have spare memory in the box and c) if your application pattern
>> after testing benefits that approach (which stuff with heaving
>> sorting, hashing, temp table usage will) - see my blog entry: Put
>> TEMPDB on a RAM DRIVE; Short lived # tables - do they get written to
>> disk?
>> (http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/08/24/958.aspx)
>> --
>> Tony Rogerson
>> SQL Server MVP
>> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from
>> a SQL Server Consultant
>> http://sqlserverfaq.com - free video tutorials
>>
>> "OD" <oludan@.hotmail.com> wrote in message
>> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>>I just acquire a new server with 8 hard drives and 2 RAID controllers.
>>The objective is to load SQL SERVER 2005 on this server to run CRM and
>>one other database centric application. In addition rerporting
>>services and analysis services will also be installed. I have
>>configured two of the RAID hard disks as RAID1 and created the System
>>partition on it as Drive C (30GB) and the remaining as Drive D.
>> I configured another 2 as RAID1 (67GB) which I intend to use for the
>> Databases log files.
>> I now have 4 hard disks left. I can either configure this drives as 1
>> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much
>> of an issue here, I am trying to achieve the best possible
>> performance. Which RAID configuration is better for the data files?
>> Any suggestions or recommendations?
>> Thank you,
>> OD
>>
>>
>>
>>
>
Hard disk configuration question
I just acquire a new server with 8 hard drives and 2 RAID controllers. The
objective is to load SQL SERVER 2005 on this server to run CRM and one other
database centric application. In addition rerporting services and analysis
services will also be installed. I have configured two of the RAID hard
disks as RAID1 and created the System partition on it as Drive C (30GB) and
the remaining as Drive D.
I configured another 2 as RAID1 (67GB) which I intend to use for the
Databases log files.
I now have 4 hard disks left. I can either configure this drives as 1 RAID5
Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an issue
here, I am trying to achieve the best possible performance. Which RAID
configuration is better for the data files? Any suggestions or
recommendations?
Thank you,
ODMake the 4 hard drives RAID 10 (mirror then striping).
Don't even touch RAID 5 with a barge poll now-a-days.
Put tempdb on the D: on its own RAID 1 array away from the second and third
arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
recommending it has its own uncontended array and even use a RAM disk if a)
the RAM disk fully supports SQL Server IO requirements and b) you have spare
memory in the box and c) if your application pattern after testing benefits
that approach (which stuff with heaving sorting, hashing, temp table usage
will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short lived # tables -
do they get written to disk?
(http://sqlblogcasts.com/blogs/tonyr.../08/24/958.aspx)
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||With 8 drives, my suggestion for best performance is:
Two Drives -RAID 1 (log files)
Three Drives RAID 0
Three Drives RAID 0
Mirror the above two RAID 0 sets, making a RAID 10.
Use the RAID 10 for OS and datafiles.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||Thats RAID 01 which isn't as fault tolerant as RAID 10.
01 is striping and then mirroring the stripe; if a disk in the stripe fails
then your whole array is exposed and a single drive failure on the second
mirrored striped can cause the set to be unavailable.
10 is mirror the drives and then stripe across, if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for the
one that failed then you are ok.
Basically, you can lose more drives RAID 10 then with RAID 01.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
> With 8 drives, my suggestion for best performance is:
> Two Drives -RAID 1 (log files)
> Three Drives RAID 0
> Three Drives RAID 0
> Mirror the above two RAID 0 sets, making a RAID 10.
> Use the RAID 10 for OS and datafiles.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>|||Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
locate the Data files for Tempdb on the RAID 10 set with other user create
data files?
here is what I will have:
-RAID 1: partitioned to DRIVE C (for System) and D (May be backup and other
media files).
-RAID 1: Partioned to E (for logs) and F: for backup
-RAID 10: Partioned to G and H for different data files
what do you think?
OD
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
> Make the 4 hard drives RAID 10 (mirror then striping).
> Don't even touch RAID 5 with a barge poll now-a-days.
> Put tempdb on the D: on its own RAID 1 array away from the second and
> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
> recommending it has its own uncontended array and even use a RAM disk if
> a) the RAM disk fully supports SQL Server IO requirements and b) you have
> spare memory in the box and c) if your application pattern after testing
> benefits that approach (which stuff with heaving sorting, hashing, temp
> table usage will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short
> lived # tables - do they get written to disk?
> (http://sqlblogcasts.com/blogs/tonyr.../08/24/958.aspx)
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>|||Hi OD,
> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
> other user create data files?
Why? Your system should rarely ever page so disk performance to the RAID 1
array containing pagefile.sys should not be a problem - better to utilise
it, if your box is paging (thereby causing IO to that RAID 1 array) then you
have other memory problems to solve first anyway, by using D: you aren't
touching the logical system drive so you will have enough space to put the
pagefile.sys (fix this rather than allow OS to grow it).
Think of tempdb in the same way you think of a database transaction log.
Why have RAID 10 partitioned as G and H? Just make it one logical drive -
drive G:
Again, why partition RAID 1 as E: and F: - just make it one logical drive -
drive E:
When you format the partitions in NT, format them NTFS but give it an
allocation size that matches your RAID stripe size, its usually 64K.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
> Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
> they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
> locate the Data files for Tempdb on the RAID 10 set with other user create
> data files?
> here is what I will have:
> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
> other media files).
> -RAID 1: Partioned to E (for logs) and F: for backup
> -RAID 10: Partioned to G and H for different data files
> what do you think?
> OD
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>|||Thanks Tony, for the additional information.
However, as I was apt to do in my many Econ classes, I love to challenge the
assumptions. Anytime there is an 'IF', as in:
"if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for
the
one that failed then you are ok"
It seems mirrored stripes AND stripped mirrors are both vulnerable to
multiple drive failures. However, as you indicated, the stripped mirrors
seem to provide a little bit more of a element of chance to which mirrored
drive fails, whereas with mirrored stripes, failure in the mirror is certain
'death'.
One could posit that all of society survives on the element of chance.
Another day, another useful bit of information gleaned.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
> Thats RAID 01 which isn't as fault tolerant as RAID 10.
> 01 is striping and then mirroring the stripe; if a disk in the stripe
> fails then your whole array is exposed and a single drive failure on the
> second mirrored striped can cause the set to be unavailable.
> 10 is mirror the drives and then stripe across, if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for the
> one that failed then you are ok.
> Basically, you can lose more drives RAID 10 then with RAID 01.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>|||Thank you all for the assistance. In that case, I will stick with your
earlier advice as so:
First RAID 1
--C: ->System and Binary
--D: -> TempDB
Second Raid 1
--E: -> LOGS + Backup
RAID 10
--F: Data files
Now that the DB spaces have been figured out will it be ok (performance
wise) for one of Drives D, E or F to also hold other data such as Word and
Excel files that are generated by one of the appliations?
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
> Hi OD,
>
> Why? Your system should rarely ever page so disk performance to the RAID 1
> array containing pagefile.sys should not be a problem - better to utilise
> it, if your box is paging (thereby causing IO to that RAID 1 array) then
> you have other memory problems to solve first anyway, by using D: you
> aren't touching the logical system drive so you will have enough space to
> put the pagefile.sys (fix this rather than allow OS to grow it).
> Think of tempdb in the same way you think of a database transaction log.
> Why have RAID 10 partitioned as G and H? Just make it one logical drive -
> drive G:
> Again, why partition RAID 1 as E: and F: - just make it one logical
> drive - drive E:
> When you format the partitions in NT, format them NTFS but give it an
> allocation size that matches your RAID stripe size, its usually 64K.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>|||You raise a good point.
Something else I've seen is that all the onboard SATA RAID controllers I've
seen so far implement RAID 01, so if you want RAID 10 you must RAID 1 the
drives first and then use Windows to stripe across the drives.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>|||I am running a DELL PERC 5 RAID controller and it explains this same thing.
However, it only allows configuration for RAIDs 0, 1, 5, and 10. So I have
configured the last 4 drives as RAID 10 since it's the only option supported
on the controller between RAID 01 and RAID 10.
thank you for your assistance.
OD
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>
objective is to load SQL SERVER 2005 on this server to run CRM and one other
database centric application. In addition rerporting services and analysis
services will also be installed. I have configured two of the RAID hard
disks as RAID1 and created the System partition on it as Drive C (30GB) and
the remaining as Drive D.
I configured another 2 as RAID1 (67GB) which I intend to use for the
Databases log files.
I now have 4 hard disks left. I can either configure this drives as 1 RAID5
Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an issue
here, I am trying to achieve the best possible performance. Which RAID
configuration is better for the data files? Any suggestions or
recommendations?
Thank you,
ODMake the 4 hard drives RAID 10 (mirror then striping).
Don't even touch RAID 5 with a barge poll now-a-days.
Put tempdb on the D: on its own RAID 1 array away from the second and third
arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
recommending it has its own uncontended array and even use a RAM disk if a)
the RAM disk fully supports SQL Server IO requirements and b) you have spare
memory in the box and c) if your application pattern after testing benefits
that approach (which stuff with heaving sorting, hashing, temp table usage
will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short lived # tables -
do they get written to disk?
(http://sqlblogcasts.com/blogs/tonyr.../08/24/958.aspx)
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||With 8 drives, my suggestion for best performance is:
Two Drives -RAID 1 (log files)
Three Drives RAID 0
Three Drives RAID 0
Mirror the above two RAID 0 sets, making a RAID 10.
Use the RAID 10 for OS and datafiles.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"OD" <oludan@.hotmail.com> wrote in message
news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>I just acquire a new server with 8 hard drives and 2 RAID controllers. The
>objective is to load SQL SERVER 2005 on this server to run CRM and one
>other database centric application. In addition rerporting services and
>analysis services will also be installed. I have configured two of the RAID
>hard disks as RAID1 and created the System partition on it as Drive C
>(30GB) and the remaining as Drive D.
> I configured another 2 as RAID1 (67GB) which I intend to use for the
> Databases log files.
> I now have 4 hard disks left. I can either configure this drives as 1
> RAID5 Vitual Disk or 2 RAID1 Vitual Disk.Since space is not so much of an
> issue here, I am trying to achieve the best possible performance. Which
> RAID configuration is better for the data files? Any suggestions or
> recommendations?
> Thank you,
> OD
>|||Thats RAID 01 which isn't as fault tolerant as RAID 10.
01 is striping and then mirroring the stripe; if a disk in the stripe fails
then your whole array is exposed and a single drive failure on the second
mirrored striped can cause the set to be unavailable.
10 is mirror the drives and then stripe across, if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for the
one that failed then you are ok.
Basically, you can lose more drives RAID 10 then with RAID 01.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
> With 8 drives, my suggestion for best performance is:
> Two Drives -RAID 1 (log files)
> Three Drives RAID 0
> Three Drives RAID 0
> Mirror the above two RAID 0 sets, making a RAID 10.
> Use the RAID 10 for OS and datafiles.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>|||Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
locate the Data files for Tempdb on the RAID 10 set with other user create
data files?
here is what I will have:
-RAID 1: partitioned to DRIVE C (for System) and D (May be backup and other
media files).
-RAID 1: Partioned to E (for logs) and F: for backup
-RAID 10: Partioned to G and H for different data files
what do you think?
OD
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
> Make the 4 hard drives RAID 10 (mirror then striping).
> Don't even touch RAID 5 with a barge poll now-a-days.
> Put tempdb on the D: on its own RAID 1 array away from the second and
> third arrays, tempdb in SQL 2005 is more heavily used but even in 2000 I'm
> recommending it has its own uncontended array and even use a RAM disk if
> a) the RAM disk fully supports SQL Server IO requirements and b) you have
> spare memory in the box and c) if your application pattern after testing
> benefits that approach (which stuff with heaving sorting, hashing, temp
> table usage will) - see my blog entry: Put TEMPDB on a RAM DRIVE; Short
> lived # tables - do they get written to disk?
> (http://sqlblogcasts.com/blogs/tonyr.../08/24/958.aspx)
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:ePVRL72yGHA.4844@.TK2MSFTNGP04.phx.gbl...
>|||Hi OD,
> Is it ok to locate the Data files for Tempdb on the RAID 10 set with
> other user create data files?
Why? Your system should rarely ever page so disk performance to the RAID 1
array containing pagefile.sys should not be a problem - better to utilise
it, if your box is paging (thereby causing IO to that RAID 1 array) then you
have other memory problems to solve first anyway, by using D: you aren't
touching the logical system drive so you will have enough space to put the
pagefile.sys (fix this rather than allow OS to grow it).
Think of tempdb in the same way you think of a database transaction log.
Why have RAID 10 partitioned as G and H? Just make it one logical drive -
drive G:
Again, why partition RAID 1 as E: and F: - just make it one logical drive -
drive E:
When you format the partitions in NT, format them NTFS but give it an
allocation size that matches your RAID stripe size, its usually 64K.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"OD" <oludan@.hotmail.com> wrote in message
news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
> Thanks for the recomendation. Drive C and D are on the same RAID 1 set but
> they are 2 different OS partition on the RAID Vitual Disk. Is it ok to
> locate the Data files for Tempdb on the RAID 10 set with other user create
> data files?
> here is what I will have:
> -RAID 1: partitioned to DRIVE C (for System) and D (May be backup and
> other media files).
> -RAID 1: Partioned to E (for logs) and F: for backup
> -RAID 10: Partioned to G and H for different data files
> what do you think?
> OD
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:eQ7X2i3yGHA.2640@.TK2MSFTNGP06.phx.gbl...
>|||Thanks Tony, for the additional information.
However, as I was apt to do in my many Econ classes, I love to challenge the
assumptions. Anytime there is an 'IF', as in:
"if a disk in the stripe
fails then so long as a disk in the mirror stripe isn't the mirror for
the
one that failed then you are ok"
It seems mirrored stripes AND stripped mirrors are both vulnerable to
multiple drive failures. However, as you indicated, the stripped mirrors
seem to provide a little bit more of a element of chance to which mirrored
drive fails, whereas with mirrored stripes, failure in the mirror is certain
'death'.
One could posit that all of society survives on the element of chance.
Another day, another useful bit of information gleaned.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
> Thats RAID 01 which isn't as fault tolerant as RAID 10.
> 01 is striping and then mirroring the stripe; if a disk in the stripe
> fails then your whole array is exposed and a single drive failure on the
> second mirrored striped can cause the set to be unavailable.
> 10 is mirror the drives and then stripe across, if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for the
> one that failed then you are ok.
> Basically, you can lose more drives RAID 10 then with RAID 01.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:u3zHWl3yGHA.4596@.TK2MSFTNGP02.phx.gbl...
>|||Thank you all for the assistance. In that case, I will stick with your
earlier advice as so:
First RAID 1
--C: ->System and Binary
--D: -> TempDB
Second Raid 1
--E: -> LOGS + Backup
RAID 10
--F: Data files
Now that the DB spaces have been figured out will it be ok (performance
wise) for one of Drives D, E or F to also hold other data such as Word and
Excel files that are generated by one of the appliations?
"Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
news:uzfHy73yGHA.5048@.TK2MSFTNGP05.phx.gbl...
> Hi OD,
>
> Why? Your system should rarely ever page so disk performance to the RAID 1
> array containing pagefile.sys should not be a problem - better to utilise
> it, if your box is paging (thereby causing IO to that RAID 1 array) then
> you have other memory problems to solve first anyway, by using D: you
> aren't touching the logical system drive so you will have enough space to
> put the pagefile.sys (fix this rather than allow OS to grow it).
> Think of tempdb in the same way you think of a database transaction log.
> Why have RAID 10 partitioned as G and H? Just make it one logical drive -
> drive G:
> Again, why partition RAID 1 as E: and F: - just make it one logical
> drive - drive E:
> When you format the partitions in NT, format them NTFS but give it an
> allocation size that matches your RAID stripe size, its usually 64K.
> --
> Tony Rogerson
> SQL Server MVP
> http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a
> SQL Server Consultant
> http://sqlserverfaq.com - free video tutorials
>
> "OD" <oludan@.hotmail.com> wrote in message
> news:eWT2923yGHA.4232@.TK2MSFTNGP05.phx.gbl...
>|||You raise a good point.
Something else I've seen is that all the onboard SATA RAID controllers I've
seen so far implement RAID 01, so if you want RAID 10 you must RAID 1 the
drives first and then use Windows to stripe across the drives.
Tony Rogerson
SQL Server MVP
http://sqlblogcasts.com/blogs/tonyrogerson - technical commentary from a SQL
Server Consultant
http://sqlserverfaq.com - free video tutorials
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>|||I am running a DELL PERC 5 RAID controller and it explains this same thing.
However, it only allows configuration for RAIDs 0, 1, 5, and 10. So I have
configured the last 4 drives as RAID 10 since it's the only option supported
on the controller between RAID 01 and RAID 10.
thank you for your assistance.
OD
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:e9%23BGC4yGHA.4968@.TK2MSFTNGP05.phx.gbl...
> Thanks Tony, for the additional information.
> However, as I was apt to do in my many Econ classes, I love to challenge
> the assumptions. Anytime there is an 'IF', as in:
> "if a disk in the stripe
> fails then so long as a disk in the mirror stripe isn't the mirror for
> the
> one that failed then you are ok"
> It seems mirrored stripes AND stripped mirrors are both vulnerable to
> multiple drive failures. However, as you indicated, the stripped mirrors
> seem to provide a little bit more of a element of chance to which mirrored
> drive fails, whereas with mirrored stripes, failure in the mirror is
> certain 'death'.
> One could posit that all of society survives on the element of chance.
> Another day, another useful bit of information gleaned.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Tony Rogerson" <tonyrogerson@.sqlserverfaq.com> wrote in message
> news:uoxYHr3yGHA.3656@.TK2MSFTNGP04.phx.gbl...
>
Subscribe to:
Comments (Atom)