Consistency Error in Checkdb

When I use DBCC CHECKDB I got allocation errors and
consistency errors. I use CHECKDB with
repair_allow_data_loss to fix it. It can fix the
allocation errors, but the consistency errors are still
there. How can I fix consistency errors?
Thanks,
Monica.First you need to check if you have any hardware issues or not. If you have any hardware problem you need to fix them first. If the number of errors don't happen to reduce, you can then mark the database in emergency mode and DTS the objects and data to a new database on the server. Once the transfer completes, make sure you run DBCC CHECKDB on the new database. Once it comes out clean, drop the problem database, rename the new database to the old one
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/info/cpyright.ht|||Monica,
It depends what the errors are and which objects they are in. A very small
number of errors on critical tables cannot be repaired, in which case
you'll need to restore from your backups or extract as much information as
you can as suggested in the other reply.
Microsoft recommends that you have a backup strategy that allows you to
recover from hardware-caused corruptions rather than using the
REPAIR_ALLOW_DATA_LOSS option to CHECKDB, which as its name implies may have
to delete data to get the database back to a structurally consistent state.
If you're still stuck, please call Product Support
(http://support.microsoft.com) who will be able to assist you.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Monica Clinton" <hv37@.yahoo.com> wrote in message
news:2fe501c3e1d1$9aef89f0$a001280a@.phx.gbl...
> When I use DBCC CHECKDB I got allocation errors and
> consistency errors. I use CHECKDB with
> repair_allow_data_loss to fix it. It can fix the
> allocation errors, but the consistency errors are still
> there. How can I fix consistency errors?
> Thanks,
> Monica.|||Thanks for you help.
We fixed the hardware problem, now we are trying to fix
the data. How do I mark the database in emergency mode?
When we DTS the data to a new database, we had the same
errors. How to fix the errors?
Thank you.
Monica
>--Original Message--
>First you need to check if you have any hardware issues
or not. If you have any hardware problem you need to fix
them first. If the number of errors don't happen to
reduce, you can then mark the database in emergency mode
and DTS the objects and data to a new database on the
server. Once the transfer completes, make sure you run
DBCC CHECKDB on the new database. Once it comes out clean,
drop the problem database, rename the new database to the
old one.
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>http://www.microsoft.com/info/cpyright.htm
>
>.
>

Consistency Error in Checkdb

When I use DBCC CHECKDB I got allocation errors and
consistency errors. I use CHECKDB with
repair_allow_data_loss to fix it. It can fix the
allocation errors, but the consistency errors are still
there. How can I fix consistency errors?
Thanks,
Monica.First you need to check if you have any hardware issues or not. If you have
any hardware problem you need to fix them first. If the number of errors don
't happen to reduce, you can then mark the database in emergency mode and DT
S the objects and data to a
new database on the server. Once the transfer completes, make sure you run D
BCC CHECKDB on the new database. Once it comes out clean, drop the problem d
atabase, rename the new database to the old one.
This posting is provided "AS IS" with no warranties, and confers no rights.
http://www.microsoft.com/info/cpyright.htm|||Monica,
It depends what the errors are and which objects they are in. A very small
number of errors on critical tables cannot be repaired, in which case
you'll need to restore from your backups or extract as much information as
you can as suggested in the other reply.
Microsoft recommends that you have a backup strategy that allows you to
recover from hardware-caused corruptions rather than using the
REPAIR_ALLOW_DATA_LOSS option to CHECKDB, which as its name implies may have
to delete data to get the database back to a structurally consistent state.
If you're still stuck, please call Product Support
(http://support.microsoft.com) who will be able to assist you.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Monica Clinton" <hv37@.yahoo.com> wrote in message
news:2fe501c3e1d1$9aef89f0$a001280a@.phx.gbl...

quote:

---

> When I use DBCC CHECKDB I got allocation errors and
> consistency errors. I use CHECKDB with
> repair_allow_data_loss to fix it. It can fix the
> allocation errors, but the consistency errors are still
> there. How can I fix consistency errors?
> Thanks,
> Monica.

---

|||Thanks for you help.
We fixed the hardware problem, now we are trying to fix
the data. How do I mark the database in emergency mode?
When we DTS the data to a new database, we had the same
errors. How to fix the errors?
Thank you.
Monica

quote:

---

>--Original Message--
>First you need to check if you have any hardware issues

---

or not. If you have any hardware problem you need to fix
them first. If the number of errors don't happen to
reduce, you can then mark the database in emergency mode
and DTS the objects and data to a new database on the
server. Once the transfer completes, make sure you run
DBCC CHECKDB on the new database. Once it comes out clean,
drop the problem database, rename the new database to the
old one.

quote:

---

>This posting is provided "AS IS" with no warranties, and

---

confers no rights.

quote:

---

>http://www.microsoft.com/info/cpyright.htm
>
>.
>

---

connection problems

Hello,

My application is having a problem connecting to its database. The error I am getting is below...

Can anyone give me a pointer on how to fix the problem... I am guessing I need to increase the authentication or change how the database is accessed?

thanks

Cannot open user default database. Login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.Data.SqlClient.SqlException: Cannot open user default database. Login failed.
Login failed for user 'NT AUTHORITY\NETWORK SERVICE'.

Hi,

This means that your ASPNET worker ('NT AUTHORITY\NETWORK SERVICE')does not have access to your datasource.

If you are using SQL Server, there stages of the SQL server access which you have to set in your SQL Server:

1. Add login users in your SQL Server (add your ASPNET worker)

2. Grant access to database to this

3. Grant access to dabase object (Stored procs, tables, etc)

I hope this helps.

Cheers,

Wilmar, KSA (Mabuhay!)