Home > Archive > MS SQL Server > October 2006 > consistency errors and prevention









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author consistency errors and prevention
Stedak

2006-10-24, 6:38 pm

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.
Andrew J. Kelly

2006-10-24, 6:38 pm

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@microso
ft.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.



Greg Linwood

2006-10-24, 6:38 pm

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@microso
ft.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.



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com