Index Errors!

Hi,
Our database has been producing alot of errors in the SQL
Server Log file. Most of these errors are codes 624, 644
and 605.
What could be causing these errors to appear so
frequently? This only started recently.
We are going to perform the Stress Test as recommended on
this page http://support.microsoft.com/default.aspx?
scid=kb;en-us;826433. But we're waiting for a good time to
do this as it will take up a considerable amount of time.
Thanks!Os Sutrisno wrote:
> Hi,
> Our database has been producing alot of errors in the SQL
> Server Log file. Most of these errors are codes 624, 644
> and 605.
> What could be causing these errors to appear so
> frequently? This only started recently.
Your database looks like it has been corrupted lately. Did you try to
execute DBCC CHECKDB to determine the extent of the damage? Make sure you
have a good set of latest backups on site, they might come in handy soon.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||We've done a DBCC CheckDB and the loss was only 2 rows of
data. However, these errors still appear the following day
on another table or database.
What could be causing these corruption? Is there a way to
keep the database healthy? any maintenance that can be
done?
Thanks,
Os
>--Original Message--
>Os Sutrisno wrote:
>> Hi,
>> Our database has been producing alot of errors in the
SQL
>> Server Log file. Most of these errors are codes 624, 644
>> and 605.
>> What could be causing these errors to appear so
>> frequently? This only started recently.
>Your database looks like it has been corrupted lately.
Did you try to
>execute DBCC CHECKDB to determine the extent of the
damage? Make sure you
>have a good set of latest backups on site, they might
come in handy soon.
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||Looks like you've got bad hardware somewhere. You should check your
errorlog, the NT event logs and run all relevant hardware diagnostics on
your IO subsystem. If you need help with this, PSS
(http://support.microsoft.com) should be able to help you.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Os Sutrisno" <oswin8@.hotmail.com> wrote in message
news:718a01c4024c$402c1f60$a301280a@.phx.gbl...
> We've done a DBCC CheckDB and the loss was only 2 rows of
> data. However, these errors still appear the following day
> on another table or database.
> What could be causing these corruption? Is there a way to
> keep the database healthy? any maintenance that can be
> done?
> Thanks,
> Os
>
> >--Original Message--
> >Os Sutrisno wrote:
> >> Hi,
> >>
> >> Our database has been producing alot of errors in the
> SQL
> >> Server Log file. Most of these errors are codes 624, 644
> >> and 605.
> >>
> >> What could be causing these errors to appear so
> >> frequently? This only started recently.
> >
> >Your database looks like it has been corrupted lately.
> Did you try to
> >execute DBCC CHECKDB to determine the extent of the
> damage? Make sure you
> >have a good set of latest backups on site, they might
> come in handy soon.
> >
> >sincerely,
> >--
> >Sebastian K. Zaklada
> >Skilled Software
> >http://www.skilledsoftware.com
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >.
> >|||Os Sutrisno wrote:
> We've done a DBCC CheckDB and the loss was only 2 rows of
> data. However, these errors still appear the following day
> on another table or database.
> What could be causing these corruption? Is there a way to
> keep the database healthy? any maintenance that can be
> done?
Many things, too many to count. But you should focus on your hardware,
especially I/O subsystem (drives, controllers). Does your drive controller
use write-ahead caching? If yes, try to disable it. Be sure that your disk
controller prevents the uncontrolled reset of the caching controller, has
on-board battery backup, and uses mirrored or ECC memory. Do not implement
write caching unless the hardware vendor guarantees that the write cache
includes all features required to prevent data loss.
sincerely,
--
Sebastian K. Zaklada
Skilled Software
http://www.skilledsoftware.com
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thanks everyone!
I'll try to find out whats going wrong...
Unfortunately, the support from Microsoft in Singapore is
almost non-existent. The last time I emailed and contacted
them, they said Microsoft Singapore only provides support
for OS and Desktop Applications. I was told to contact
HP/Compaq for server applications support. But then,
Hp/Compaq wants our company to sign a yearly $50k
contract, before they'll lend a hand...
Anyways, Thanks again!
>--Original Message--
>Os Sutrisno wrote:
>> We've done a DBCC CheckDB and the loss was only 2 rows
of
>> data. However, these errors still appear the following
day
>> on another table or database.
>> What could be causing these corruption? Is there a way
to
>> keep the database healthy? any maintenance that can be
>> done?
>Many things, too many to count. But you should focus on
your hardware,
>especially I/O subsystem (drives, controllers). Does your
drive controller
>use write-ahead caching? If yes, try to disable it. Be
sure that your disk
>controller prevents the uncontrolled reset of the caching
controller, has
>on-board battery backup, and uses mirrored or ECC memory.
Do not implement
>write caching unless the hardware vendor guarantees that
the write cache
>includes all features required to prevent data loss.
>sincerely,
>--
>Sebastian K. Zaklada
>Skilled Software
>http://www.skilledsoftware.com
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>.
>|||I'll pass this feedback to the appropriate PSS management.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Os Sutrisno" <oswin8@.hotmail.com> wrote in message
news:81da01c40314$dffd5f90$a101280a@.phx.gbl...
> Thanks everyone!
> I'll try to find out whats going wrong...
> Unfortunately, the support from Microsoft in Singapore is
> almost non-existent. The last time I emailed and contacted
> them, they said Microsoft Singapore only provides support
> for OS and Desktop Applications. I was told to contact
> HP/Compaq for server applications support. But then,
> Hp/Compaq wants our company to sign a yearly $50k
> contract, before they'll lend a hand...
> Anyways, Thanks again!
> >--Original Message--
> >Os Sutrisno wrote:
> >
> >> We've done a DBCC CheckDB and the loss was only 2 rows
> of
> >> data. However, these errors still appear the following
> day
> >> on another table or database.
> >>
> >> What could be causing these corruption? Is there a way
> to
> >> keep the database healthy? any maintenance that can be
> >> done?
> >
> >Many things, too many to count. But you should focus on
> your hardware,
> >especially I/O subsystem (drives, controllers). Does your
> drive controller
> >use write-ahead caching? If yes, try to disable it. Be
> sure that your disk
> >controller prevents the uncontrolled reset of the caching
> controller, has
> >on-board battery backup, and uses mirrored or ECC memory.
> Do not implement
> >write caching unless the hardware vendor guarantees that
> the write cache
> >includes all features required to prevent data loss.
> >
> >sincerely,
> >--
> >Sebastian K. Zaklada
> >Skilled Software
> >http://www.skilledsoftware.com
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >.
> >