consistency errors and prevention

What causes consistency errors and what can be done to prevent them?
We have a large number (500 or so) of SQL Server 2000 installations with
database sizes ranging from 3 - 120 gig. Average database size would be 15-40
gig. They could be installed on Server 2000 or 2003 or something equivalent
- never on a workstation. Memory on the machines can range from 1gig to 4 gig.
We have lost close to 10 databases this year so far.
Most errors are due to hardware problems these days. A failing disk array or
controller is a key culprit in getting corrupt data. But there are other
reasons as well. Bad UPS's, non-battery backed caching controllers, unstable
mother boards etc.
Andrew J. Kelly SQL MVP
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:935DF649-22D7-4B2F-9D81-189649200950@.microsoft.com...
> What causes consistency errors and what can be done to prevent them?
> We have a large number (500 or so) of SQL Server 2000 installations with
> database sizes ranging from 3 - 120 gig. Average database size would be
> 15-40
> gig. They could be installed on Server 2000 or 2003 or something
> equivalent
> - never on a workstation. Memory on the machines can range from 1gig to 4
> gig.
> We have lost close to 10 databases this year so far.
|||I'm curious what hardware are you using?
I've seen an amazingly consistent string of database corruptions on Tyan
servers recently..
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:935DF649-22D7-4B2F-9D81-189649200950@.microsoft.com...
> What causes consistency errors and what can be done to prevent them?
> We have a large number (500 or so) of SQL Server 2000 installations with
> database sizes ranging from 3 - 120 gig. Average database size would be
> 15-40
> gig. They could be installed on Server 2000 or 2003 or something
> equivalent
> - never on a workstation. Memory on the machines can range from 1gig to 4
> gig.
> We have lost close to 10 databases this year so far.
|||In addition, below article has some details on what properties you want to ensure your storage
subsystem has:
http://www.microsoft.com/technet/pro...lIObasics.mspx
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:uE4IgAO9GHA.2268@.TK2MSFTNGP05.phx.gbl...
> I'm curious what hardware are you using?
> I've seen an amazingly consistent string of database corruptions on Tyan servers recently..
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> "Stedak" <Stedak@.discussions.microsoft.com> wrote in message
> news:935DF649-22D7-4B2F-9D81-189649200950@.microsoft.com...
>

consistency errors and prevention

What causes consistency errors and what can be done to prevent them?
We have a large number (500 or so) of SQL Server 2000 installations with
database sizes ranging from 3 - 120 gig. Average database size would be 15-4
0
gig. They could be installed on Server 2000 or 2003 or something equivalent
- never on a workstation. Memory on the machines can range from 1gig to 4 gi
g.
We have lost close to 10 databases this year so far.Most errors are due to hardware problems these days. A failing disk array or
controller is a key culprit in getting corrupt data. But there are other
reasons as well. Bad UPS's, non-battery backed caching controllers, unstable
mother boards etc.
Andrew J. Kelly SQL MVP
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:935DF649-22D7-4B2F-9D81-189649200950@.microsoft.com...
> What causes consistency errors and what can be done to prevent them?
> We have a large number (500 or so) of SQL Server 2000 installations with
> database sizes ranging from 3 - 120 gig. Average database size would be
> 15-40
> gig. They could be installed on Server 2000 or 2003 or something
> equivalent
> - never on a workstation. Memory on the machines can range from 1gig to 4
> gig.
> We have lost close to 10 databases this year so far.|||I'm curious what hardware are you using?
I've seen an amazingly consistent string of database corruptions on Tyan
servers recently..
Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood
"Stedak" <Stedak@.discussions.microsoft.com> wrote in message
news:935DF649-22D7-4B2F-9D81-189649200950@.microsoft.com...
> What causes consistency errors and what can be done to prevent them?
> We have a large number (500 or so) of SQL Server 2000 installations with
> database sizes ranging from 3 - 120 gig. Average database size would be
> 15-40
> gig. They could be installed on Server 2000 or 2003 or something
> equivalent
> - never on a workstation. Memory on the machines can range from 1gig to 4
> gig.
> We have lost close to 10 databases this year so far.|||In addition, below article has some details on what properties you want to e
nsure your storage
subsystem has:
http://www.microsoft.com/technet/pr...ver/default.asp
http://www.solidqualitylearning.com/
"Greg Linwood" <g_linwood@.hotmail.com> wrote in message
news:uE4IgAO9GHA.2268@.TK2MSFTNGP05.phx.gbl...
> I'm curious what hardware are you using?
> I've seen an amazingly consistent string of database corruptions on Tyan s
ervers recently..
> Regards,
> Greg Linwood
> SQL Server MVP
> http://blogs.sqlserver.org.au/blogs/greg_linwood
> "Stedak" <Stedak@.discussions.microsoft.com> wrote in message
> news:935DF649-22D7-4B2F-9D81-189649200950@.microsoft.com...
>