Integrated Security: backup

Showing posts with label backup. Show all posts

Friday, March 30, 2012

Internal Consistency Error, Restoring Backup

Hello,
I was wondering if any body has come accross this before, and if so could
offer some advice. It's got me scratching my head.
I have a database that is backed up each night using a maintenance plan.
I have come to attempt to restore this database and it always fails with the
following error,
"An internal consistency error occured. Contact technical support for
assistance.
RESTORE DATABASE terminating abnormaly"
No matter which of the 30 odd backups from the last month I try and on any
machine, I always get the same error.
Many thanks in advance for any help offered
Yours hopefully
Chris
chris.roberts@.optima-ws.comYOu should do as the error suggests and call PSS... It is possible your
database has been corrupt for quite some time, and therefore all of your
backups are also corrupt...
"Chris Roberts" <chris.roberts@.optima-ws.com> wrote in message
news:bivr6s$39p$1@.newsg1.svr.pol.co.uk...
> Hello,
> I was wondering if any body has come accross this before, and if so could
> offer some advice. It's got me scratching my head.
> I have a database that is backed up each night using a maintenance plan.
> I have come to attempt to restore this database and it always fails with
the
> following error,
> "An internal consistency error occured. Contact technical support for
> assistance.
> RESTORE DATABASE terminating abnormaly"
> No matter which of the 30 odd backups from the last month I try and on any
> machine, I always get the same error.
> Many thanks in advance for any help offered
> Yours hopefully
> Chris
> chris.roberts@.optima-ws.com
>|||No sure if it is corrupt, one more bit off info I've found out is that if I
preform a manual backup, it restores OK, it's only when I do a backup from
the maintenance plan that I get this error. It's also the same with all the
databases, not just one
"Wayne Snyder" <wsnyder@.computeredservices.com> wrote in message
news:O3C0XfUcDHA.652@.tk2msftngp13.phx.gbl...
> YOu should do as the error suggests and call PSS... It is possible your
> database has been corrupt for quite some time, and therefore all of your
> backups are also corrupt...
> "Chris Roberts" <chris.roberts@.optima-ws.com> wrote in message
> news:bivr6s$39p$1@.newsg1.svr.pol.co.uk...
> > Hello,
> >
> > I was wondering if any body has come accross this before, and if so
could
> > offer some advice. It's got me scratching my head.
> >
> > I have a database that is backed up each night using a maintenance plan.
> >
> > I have come to attempt to restore this database and it always fails with
> the
> > following error,
> >
> > "An internal consistency error occured. Contact technical support for
> > assistance.
> > RESTORE DATABASE terminating abnormaly"
> >
> > No matter which of the 30 odd backups from the last month I try and on
any
> > machine, I always get the same error.
> >
> > Many thanks in advance for any help offered
> >
> > Yours hopefully
> >
> > Chris
> > chris.roberts@.optima-ws.com
> >
> >
>

internal consistency error occurred while restoring a database

this is what i get when restoring a database from a *.bak file, knowing that this is the only backup file i have for my DELETED databases !!!
please help ASAP
Microsoft SQL-DMO (ODBC SQLState: 42000)
An internal consistency error occurred. Contact Technical Support for assistance.
RESTORE DATABASE is terminating abnormally.
I would try what the message suggests: contact PSS.
David Portas
SQL Server MVP

internal consistency error occurred while restoring a database

this is what i get when restoring a database from a *.bak file, knowing that this is the only backup file i have for my DELETED databases !!
please help ASA
Microsoft SQL-DMO (ODBC SQLState: 42000
--
An internal consistency error occurred. Contact Technical Support for assistance
RESTORE DATABASE is terminating abnormallyi'm on SQL2K SP3,
and the file i'm restoring from is reported normally from the OS !|||I would try what the message suggests: contact PSS.
--
David Portas
SQL Server MVP
--

internal consistency error occurred while restoring a database

this is what i get when restoring a database from a *.bak file, knowing that
this is the only backup file i have for my DELETED databases !!!
please help ASAP
Microsoft SQL-DMO (ODBC SQLState: 42000)
--
An internal consistency error occurred. Contact Technical Support for assist
ance.
RESTORE DATABASE is terminating abnormally.I would try what the message suggests: contact PSS.
David Portas
SQL Server MVP
--

internal consistency error

I am getting the following error when I am trying to
restore a database/differential backup. Any ideas about
what is going on ? I can not do DBCC CHECKDB on the
production server. I will do it on the backup server if I
can restore it of course.
An internal consistency error occurred. Contact technical
support for assistance. RESTORE DATABASE is terminating
abnormally.
Thanks.
Hi,
Could you please confirm that the SQL Server is up and running and the database in question is online.
And you are unable to run DBCC CHECKDB(<db name>)
On doing so what error you get? On running DBCC CHECKDB does it shows some inconsistency and allocation error on the second last line of output...
Also look for errors in the SQL Server error log for this database.
Regards
Abid
|||Why can't you run checkdb on your production server?
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
> I am getting the following error when I am trying to
> restore a database/differential backup. Any ideas about
> what is going on ? I can not do DBCC CHECKDB on the
> production server. I will do it on the backup server if I
> can restore it of course.
> An internal consistency error occurred. Contact technical
> support for assistance. RESTORE DATABASE is terminating
> abnormally.
> Thanks.
|||Are you sure that you have a complete, valid .bak file?
|||Production database is heavyly transaction oriented and I
don't want to run into performance issues while all the
users are in. The size of the DB is ~45 GB.
Thanks.

>--Original Message--
>Why can't you run checkdb on your production server?
>--
>Paul Randal
>Dev Lead, Microsoft SQL Server Storage Engine
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
I[vbcol=seagreen]
technical
>
>.
>
|||Yes I do. Actually, I am getting the error when I am
restoring the Differential backup. And NO, there is no
other backup after the differential backup.
I have the FULL backup from sunday and the differential
backup from last night. Both backups were completed
successfully.

>--Original Message--
>Are you sure that you have a complete, valid .bak file?
>.
>
sql

internal consistency error

I am getting the following error when I am trying to
restore a database/differential backup. Any ideas about
what is going on ' I can not do DBCC CHECKDB on the
production server. I will do it on the backup server if I
can restore it of course.
An internal consistency error occurred. Contact technical
support for assistance. RESTORE DATABASE is terminating
abnormally.
Thanks.Hi,
Could you please confirm that the SQL Server is up and running and the datab
ase in question is online.
And you are unable to run DBCC CHECKDB(<db name> )
On doing so what error you get? On running DBCC CHECKDB does it shows some i
nconsistency and allocation error on the second last line of output...
Also look for errors in the SQL Server error log for this database.
Regards
Abid|||Why can't you run checkdb on your production server?
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
> I am getting the following error when I am trying to
> restore a database/differential backup. Any ideas about
> what is going on ' I can not do DBCC CHECKDB on the
> production server. I will do it on the backup server if I
> can restore it of course.
> An internal consistency error occurred. Contact technical
> support for assistance. RESTORE DATABASE is terminating
> abnormally.
> Thanks.|||Are you sure that you have a complete, valid .bak file?|||Production database is heavyly transaction oriented and I
don't want to run into performance issues while all the
users are in. The size of the DB is ~45 GB.
Thanks.

>--Original Message--
>Why can't you run checkdb on your production server?
>--
>Paul Randal
>Dev Lead, Microsoft SQL Server Storage Engine
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message
>news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
I[vbcol=seagreen]
technical[vbcol=seagreen]
>
>.
>|||Yes I do. Actually, I am getting the error when I am
restoring the Differential backup. And NO, there is no
other backup after the differential backup.
I have the FULL backup from sunday and the differential
backup from last night. Both backups were completed
successfully.

>--Original Message--
>Are you sure that you have a complete, valid .bak file?
>.
>

internal consistency error

I am getting the following error when I am trying to
restore a database/differential backup. Any ideas about
what is going on ' I can not do DBCC CHECKDB on the
production server. I will do it on the backup server if I
can restore it of course.
An internal consistency error occurred. Contact technical
support for assistance. RESTORE DATABASE is terminating
abnormally.
Thanks.Why can't you run checkdb on your production server?
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Tony" <anonymous@.discussions.microsoft.com> wrote in message
news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
> I am getting the following error when I am trying to
> restore a database/differential backup. Any ideas about
> what is going on ' I can not do DBCC CHECKDB on the
> production server. I will do it on the backup server if I
> can restore it of course.
> An internal consistency error occurred. Contact technical
> support for assistance. RESTORE DATABASE is terminating
> abnormally.
> Thanks.|||Are you sure that you have a complete, valid .bak file?|||Production database is heavyly transaction oriented and I
don't want to run into performance issues while all the
users are in. The size of the DB is ~45 GB.
Thanks.
>--Original Message--
>Why can't you run checkdb on your production server?
>--
>Paul Randal
>Dev Lead, Microsoft SQL Server Storage Engine
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>"Tony" <anonymous@.discussions.microsoft.com> wrote in
message
>news:f56601c43dca$1cce0b50$a501280a@.phx.gbl...
>> I am getting the following error when I am trying to
>> restore a database/differential backup. Any ideas about
>> what is going on ' I can not do DBCC CHECKDB on the
>> production server. I will do it on the backup server if
I
>> can restore it of course.
>> An internal consistency error occurred. Contact
technical
>> support for assistance. RESTORE DATABASE is terminating
>> abnormally.
>> Thanks.
>
>.
>|||Yes I do. Actually, I am getting the error when I am
restoring the Differential backup. And NO, there is no
other backup after the differential backup.
I have the FULL backup from sunday and the differential
backup from last night. Both backups were completed
successfully.
>--Original Message--
>Are you sure that you have a complete, valid .bak file?
>.
>

internal consistency error

I have a sql database
I run dbcc checkdb and get no errors
I go to backup the database in enterprise manager, and it won't
restore because it has internal consistency errors
I can go back to an older version of the database

I run a particular procedure in our accounting software package
Never do I get errors when running dbcc checkdb

Sometimes I get the backup and restore problem, sometimes I don't

I am doing this on a test server with about 220 megs of RAM

I am trying the dbcc checkdb ('dbname',REPAIR_REBUILD) command

Any other ideas?An update to the problem:

I ran the process on my test server on a one-gig or so database and it
runs fine but gets an internal consistency error when I backup and try
to restore (dbcc checkdb, with and without REPAIR_REBUILD, runs just
fine)

But I run the process on the real server and it backs up and restores
just fine

So .........

It points to a resource problem on the test server

But I am not sure of this

Any feedback on this from anyone?|||brucestromcpa@.aol.com (bruce strom) wrote in message news:<8a9196fd.0310300827.41041bda@.posting.google.com>...
> An update to the problem:
> I ran the process on my test server on a one-gig or so database and it
> runs fine but gets an internal consistency error when I backup and try
> to restore (dbcc checkdb, with and without REPAIR_REBUILD, runs just
> fine)
> But I run the process on the real server and it backs up and restores
> just fine
> So .........
> It points to a resource problem on the test server
> But I am not sure of this
> Any feedback on this from anyone?

A consistency error means that the backup set is corrupt, for some
reason. That could mean a hardware issue, or a bad tape, or perhaps
backing up across an unreliable network. There are also issues if the
two versions of MSSQL are not the same. Perhaps you can give some more
details - where are you backing up to (tape, local drive, network
drive)? What version of MSSQL do you have? What's the operating system
and filesystem? As a minimum test, is this reliable on your test
server:

backup database MyDB to disk = 'c:\MyDB.bak' -- or another local drive
restore database MyDB from disk = 'c:\MyDB.bak'

If that isn't reliable, do OS-level tools detect any integrity issues
with the filesystem?

Simon

Wednesday, March 21, 2012

Interesting question

hi,
I am thinking if Transactional backup is based on the data in the
Transaction Log. what if i set up a the Log Reader to be run every 1 hour,
but within that 1 hour, i do a transactional backup and issue the command
"CheckPoint"!!! Can the log reader still be able to read what i have changed
before the backup?
Thanks
Ed
Ed,
transactions are only removed from the transaction log once sp_repldone has
been issued. This is called by the log reader agent, so backing up the log,
using simple recovery mode, issuing checkpoints etc won't make any
difference.
HTH,
Paul Ibison, SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||transactions are never removed from the log otherwise doing any form of
recovery using the log would be useless. Rather they are marked as
replicated.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:%23X7hZXnKFHA.3512@.TK2MSFTNGP15.phx.gbl...
> Ed,
> transactions are only removed from the transaction log once sp_repldone
has
> been issued. This is called by the log reader agent, so backing up the
log,
> using simple recovery mode, issuing checkpoints etc won't make any
> difference.
> HTH,
> Paul Ibison, SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks for the correction! What I meant is that they can
be removed on backup of the log or truncation, although
my Englissh let me down

Rgds,
Paul
|||I thought that was what you meant, but it wasn't clear

And you know me -
I am very easily confused.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:142101c52afc$b2e69bf0$a601280a@.phx.gbl...
> Thanks for the correction! What I meant is that they can
> be removed on backup of the log or truncation, although
> my Englissh let me down

> Rgds,
> Paul
>

Interesting Maintenance Plan Problem

SQL Server 2005 - I created a maintenance plan to backup several
databases. The steps in the maintenance plan are very simple, first -
check database integrity, next reindex or reorganize the indexes, backup
the databases and finally remove backup files.
I set the schedule to begin at 12:05am and tested the process by
manually running (right-click on the job and start at step). The
process ran successfully, all steps.
That night, the process started at 12:05 and failed after the second
step with no indication why the process failed. I ran it manually and
it completed successfully. The following night the process failed after
the first step completed, again with no indication why the process
failed. Again, I ran the process manually and it completed all steps
successfully.
I modified the schedule to run at 12:30am instead - and all steps
completed successfully.
Does anybody have any ideas why the process would fail when scheduled to
run at 12:05, but not fail when scheduled to run at 12:30?
JeffDid something have the database in use?
Jeffrey Williams wrote:
> SQL Server 2005 - I created a maintenance plan to backup several
> databases. The steps in the maintenance plan are very simple, first -
> check database integrity, next reindex or reorganize the indexes, backup
> the databases and finally remove backup files.
> I set the schedule to begin at 12:05am and tested the process by
> manually running (right-click on the job and start at step). The
> process ran successfully, all steps.
> That night, the process started at 12:05 and failed after the second
> step with no indication why the process failed. I ran it manually and
> it completed successfully. The following night the process failed after
> the first step completed, again with no indication why the process
> failed. Again, I ran the process manually and it completed all steps
> successfully.
> I modified the schedule to run at 12:30am instead - and all steps
> completed successfully.
> Does anybody have any ideas why the process would fail when scheduled to
> run at 12:05, but not fail when scheduled to run at 12:30?
> Jeff
--
Brett I. Holcomb
brettholcomb@.R777bellsouth.net
Remove R777 to email|||Jeffrey
Have you looked at ERROR.LOG ? Any entries?
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
> SQL Server 2005 - I created a maintenance plan to backup several
> databases. The steps in the maintenance plan are very simple, first -
> check database integrity, next reindex or reorganize the indexes, backup
> the databases and finally remove backup files.
> I set the schedule to begin at 12:05am and tested the process by manually
> running (right-click on the job and start at step). The process ran
> successfully, all steps.
> That night, the process started at 12:05 and failed after the second step
> with no indication why the process failed. I ran it manually and it
> completed successfully. The following night the process failed after the
> first step completed, again with no indication why the process failed.
> Again, I ran the process manually and it completed all steps successfully.
> I modified the schedule to run at 12:30am instead - and all steps
> completed successfully.
> Does anybody have any ideas why the process would fail when scheduled to
> run at 12:05, but not fail when scheduled to run at 12:30?
> Jeff|||Uri,
I looked in every log I could find - no errors, just the job stopped,
reporting a failure.
Jeff
Uri Dimant wrote:
> Jeffrey
> Have you looked at ERROR.LOG ? Any entries?
>
>
> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
> news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
>> SQL Server 2005 - I created a maintenance plan to backup several
>> databases. The steps in the maintenance plan are very simple, first -
>> check database integrity, next reindex or reorganize the indexes, backup
>> the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by manually
>> running (right-click on the job and start at step). The process ran
>> successfully, all steps.
>> That night, the process started at 12:05 and failed after the second step
>> with no indication why the process failed. I ran it manually and it
>> completed successfully. The following night the process failed after the
>> first step completed, again with no indication why the process failed.
>> Again, I ran the process manually and it completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps
>> completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled to
>> run at 12:05, but not fail when scheduled to run at 12:30?
>> Jeff
>
>|||Brett,
There are no other scheduled jobs at that time, except for the
transaction log files that run every 15 minutes and take less than a
minute to run at that time (no users on the system at midnight).
Jeff
Brett I. Holcomb wrote:
> Did something have the database in use?
>
> Jeffrey Williams wrote:
>> SQL Server 2005 - I created a maintenance plan to backup several
>> databases. The steps in the maintenance plan are very simple, first
>> - check database integrity, next reindex or reorganize the indexes,
>> backup the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by
>> manually running (right-click on the job and start at step). The
>> process ran successfully, all steps.
>> That night, the process started at 12:05 and failed after the second
>> step with no indication why the process failed. I ran it manually
>> and it completed successfully. The following night the process
>> failed after the first step completed, again with no indication why
>> the process failed. Again, I ran the process manually and it
>> completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps
>> completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled
>> to run at 12:05, but not fail when scheduled to run at 12:30?
>> Jeff
>|||How about the report file for the maint plan? Anything there?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
news:4659B188.5000608@.verizon.net...
> Uri,
> I looked in every log I could find - no errors, just the job stopped, reporting a failure.
> Jeff
> Uri Dimant wrote:
>> Jeffrey
>> Have you looked at ERROR.LOG ? Any entries?
>>
>>
>> "Jeffrey Williams" <jeff.williams3188@.verizon.net> wrote in message
>> news:OeWJCO$nHHA.208@.TK2MSFTNGP05.phx.gbl...
>> SQL Server 2005 - I created a maintenance plan to backup several databases. The steps in the
>> maintenance plan are very simple, first - check database integrity, next reindex or reorganize
>> the indexes, backup the databases and finally remove backup files.
>> I set the schedule to begin at 12:05am and tested the process by manually running (right-click
>> on the job and start at step). The process ran successfully, all steps.
>> That night, the process started at 12:05 and failed after the second step with no indication why
>> the process failed. I ran it manually and it completed successfully. The following night the
>> process failed after the first step completed, again with no indication why the process failed.
>> Again, I ran the process manually and it completed all steps successfully.
>> I modified the schedule to run at 12:30am instead - and all steps completed successfully.
>> Does anybody have any ideas why the process would fail when scheduled to run at 12:05, but not
>> fail when scheduled to run at 12:30?
>> Jeff
>>|||Tibor Karaszi wrote:
> How about the report file for the maint plan? Anything there?
>
Nothing there either - the job just stops. I even reviewed the default
trace file and did not find anything there.
I can schedule the process at 12:30am and leave it there, but I was
hoping somebody else had seen something like this. I will keep
researching to see if I can find anything.
Thanks,
Jeffsql

Wednesday, March 7, 2012

Integrity Check Failure

DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
Log backup and Optimizations are successful. I can’t determine if it’s
failing to run or if it’s running
and finding a problem. The logs are not indicating any reasons for failure.
Integrity check is successful on other DB’s. Thanks for being there to help.
1. Define a report file for the plan and check that report file for error messages.
2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
3. http://www.karaszi.com/SQLServer/inf...suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> Log backup and Optimizations are successful. I can’t determine if it’s
> failing to run or if it’s running
> and finding a problem. The logs are not indicating any reasons for failure.
> Integrity check is successful on other DB’s. Thanks for being there to help.
>
|||Thanks Tibor. Can you direct me to a location that indicates the procedure for
defining a report?
"Tibor Karaszi" wrote:

> 1. Define a report file for the plan and check that report file for error messages.
> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> 3. http://www.karaszi.com/SQLServer/inf...suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
>
|||EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
this option. You can also right-click an existing plan and open (something like) history and try to
find the error messages there. I don't use maint plans, so it is a little bit sketchy...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor. Can you direct me to a location that indicates the procedure for
> defining a report?
> "Tibor Karaszi" wrote:
|||Thanks for your help
"Tibor Karaszi" wrote:

> EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
> this option. You can also right-click an existing plan and open (something like) history and try to
> find the error messages there. I don't use maint plans, so it is a little bit sketchy...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
>

Integrity Check Failure

DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
Log backup and Optimizations are successful. I can’t determine if it’s
failing to run or if it’s running
and finding a problem. The logs are not indicating any reasons for failure.
Integrity check is successful on other DB’s. Thanks for being there to hel
p.1. Define a report file for the plan and check that report file for error me
ssages.
2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
3. http://www.karaszi.com/SQLServer/in..._suspect_db.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> Log backup and Optimizations are successful. I can’t determine if it’s
> failing to run or if it’s running
> and finding a problem. The logs are not indicating any reasons for failure
.
> Integrity check is successful on other DB’s. Thanks for being there to h
elp.
>|||Thanks Tibor. Can you direct me to a location that indicates the procedure f
or
defining a report?
"Tibor Karaszi" wrote:

> 1. Define a report file for the plan and check that report file for error
messages.
> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> 3. http://www.karaszi.com/SQLServer/in..._suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
>|||EM, Management, Maintenance Plans, right-click your plan to open it. The rig
ht-most ( think) tab has
this option. You can also right-click an existing plan and open (something l
ike) history and try to
find the error messages there. I don't use maint plans, so it is a little bi
t sketchy...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...[vbcol=seagreen]
> Thanks Tibor. Can you direct me to a location that indicates the procedure
for
> defining a report?
> "Tibor Karaszi" wrote:
>|||Thanks for your help
"Tibor Karaszi" wrote:

> EM, Management, Maintenance Plans, right-click your plan to open it. The r
ight-most ( think) tab has
> this option. You can also right-click an existing plan and open (something
like) history and try to
> find the error messages there. I don't use maint plans, so it is a little
bit sketchy...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
>

Integrity Check Failure

DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
Log backup and Optimizations are successful. I canâ't determine if itâ's
failing to run or if itâ's running
and finding a problem. The logs are not indicating any reasons for failure.
Integrity check is successful on other DBâ's. Thanks for being there to help.1. Define a report file for the plan and check that report file for error messages.
2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> Log backup and Optimizations are successful. I canâ't determine if itâ's
> failing to run or if itâ's running
> and finding a problem. The logs are not indicating any reasons for failure.
> Integrity check is successful on other DBâ's. Thanks for being there to help.
>|||Thanks Tibor. Can you direct me to a location that indicates the procedure for
defining a report?
"Tibor Karaszi" wrote:
> 1. Define a report file for the plan and check that report file for error messages.
> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> 3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> > DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> > Log backup and Optimizations are successful. I canâ't determine if itâ's
> > failing to run or if itâ's running
> > and finding a problem. The logs are not indicating any reasons for failure.
> > Integrity check is successful on other DBâ's. Thanks for being there to help.
> >
>|||EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
this option. You can also right-click an existing plan and open (something like) history and try to
find the error messages there. I don't use maint plans, so it is a little bit sketchy...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
> Thanks Tibor. Can you direct me to a location that indicates the procedure for
> defining a report?
> "Tibor Karaszi" wrote:
>> 1. Define a report file for the plan and check that report file for error messages.
>> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
>> 3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
>> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
>> > DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
>> > Log backup and Optimizations are successful. I canâ't determine if itâ's
>> > failing to run or if itâ's running
>> > and finding a problem. The logs are not indicating any reasons for failure.
>> > Integrity check is successful on other DBâ's. Thanks for being there to help.
>> >
>>|||Thanks for your help
"Tibor Karaszi" wrote:
> EM, Management, Maintenance Plans, right-click your plan to open it. The right-most ( think) tab has
> this option. You can also right-click an existing plan and open (something like) history and try to
> find the error messages there. I don't use maint plans, so it is a little bit sketchy...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> news:C2AD0678-EF85-4F5B-9D99-B5B219EE9540@.microsoft.com...
> > Thanks Tibor. Can you direct me to a location that indicates the procedure for
> > defining a report?
> >
> > "Tibor Karaszi" wrote:
> >
> >> 1. Define a report file for the plan and check that report file for error messages.
> >>
> >> 2. Run DBCC CHECKDB from query analyzer using the NO_INFOMSGS options.
> >>
> >> 3. http://www.karaszi.com/SQLServer/info_corrupt_suspect_db.asp
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >>
> >>
> >> "coenzyme" <coenzyme@.discussions.microsoft.com> wrote in message
> >> news:6D6C7BC0-F4E3-496E-9BDD-0BBD8B1882A9@.microsoft.com...
> >> > DB Maintenance Plan for Integrity Check is failing. DB Backup, Transaction
> >> > Log backup and Optimizations are successful. I canâ't determine if itâ's
> >> > failing to run or if itâ's running
> >> > and finding a problem. The logs are not indicating any reasons for failure.
> >> > Integrity check is successful on other DBâ's. Thanks for being there to help.
> >> >
> >>
> >>
>

Integrity Check Errors

Hello,
I'm using SQL Server 2000 SP4 on Windows Advanced Server 2000 with latest
patches.
I use Database Maintenance Plans to backup several of my databases and I have
selected the option to check integrity before doing backup. If anything fails,
I get a net send notification.
This has been working extremely well for a year now but only lately,
Integrity checks reveals errors on random tables in random databases.
This morning I got a notification on a database called 'Planning'.
So I ran a DBCC CHECKDB('Planning') WITH NO_INFOMSGS in the Query Analyzer
just to make sure.
The following details were revealed: -
================================================================================ Server: Msg 8928, Level 16, State 1, Line 1
Object ID 1310627712, index ID 7: Page (1:3766) could not be processed. See
other errors for details.
Server: Msg 8944, Level 16, State 1, Line 1
Table error: Object ID 1310627712, index ID 7, page (1:3766), row 18. Test
(ColumnOffsets <= (nextRec - pRec)) failed. Values are 26977 and 22.
CHECKDB found 0 allocation errors and 2 consistency errors in table
'WorkTransaction' (object ID 1310627712).
CHECKDB found 0 allocation errors and 2 consistency errors in database
'Planning'.
repair_allow_data_loss is the minimum repair level for the errors found by
DBCC CHECKDB (Planning ).
================================================================================
I have been able to repair these errors by doing the following: -
1. Restrict access to Single User on this particular database.
2. In the Query Analyzer, run the statement :
USE Planning
go
DBCC CHECKTABLE('WorkTransaction', repair_allow_data_loss) WITH NO_INFOMSGS
this seems to correct the problem.
3. Remove Single User restriction.
However, I have been doing the above procedure 2 - 3 times a day on many
other databases and tables that come up with errors.
I was wondering what could be the root cause of all these sudden errors.
I use Simple Database Backup Recovery Model on all my databases.
Thanks,
Sameer.
--
Message posted via http://www.sqlmonster.comThe most likely cause of db integrity issues (especially recurring ones) is
bad hardware. I would run some intensive hardware tests to find the root
cause.
--
Andrew J. Kelly SQL MVP
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message
news:57da24b5e8956@.uwe...
> Hello,
> I'm using SQL Server 2000 SP4 on Windows Advanced Server 2000 with latest
> patches.
> I use Database Maintenance Plans to backup several of my databases and I
> have
> selected the option to check integrity before doing backup. If anything
> fails,
> I get a net send notification.
> This has been working extremely well for a year now but only lately,
> Integrity checks reveals errors on random tables in random databases.
> This morning I got a notification on a database called 'Planning'.
> So I ran a DBCC CHECKDB('Planning') WITH NO_INFOMSGS in the Query Analyzer
> just to make sure.
> The following details were revealed: -
> ================================================================================> Server: Msg 8928, Level 16, State 1, Line 1
> Object ID 1310627712, index ID 7: Page (1:3766) could not be processed.
> See
> other errors for details.
> Server: Msg 8944, Level 16, State 1, Line 1
> Table error: Object ID 1310627712, index ID 7, page (1:3766), row 18. Test
> (ColumnOffsets <= (nextRec - pRec)) failed. Values are 26977 and 22.
> CHECKDB found 0 allocation errors and 2 consistency errors in table
> 'WorkTransaction' (object ID 1310627712).
> CHECKDB found 0 allocation errors and 2 consistency errors in database
> 'Planning'.
> repair_allow_data_loss is the minimum repair level for the errors found by
> DBCC CHECKDB (Planning ).
> ================================================================================> I have been able to repair these errors by doing the following: -
> 1. Restrict access to Single User on this particular database.
> 2. In the Query Analyzer, run the statement :
> USE Planning
> go
> DBCC CHECKTABLE('WorkTransaction', repair_allow_data_loss) WITH
> NO_INFOMSGS
> this seems to correct the problem.
> 3. Remove Single User restriction.
>
> However, I have been doing the above procedure 2 - 3 times a day on many
> other databases and tables that come up with errors.
> I was wondering what could be the root cause of all these sudden errors.
> I use Simple Database Backup Recovery Model on all my databases.
> Thanks,
> Sameer.
> --
> Message posted via http://www.sqlmonster.com|||Thanks Andrew,
I forgot to mention that I did a comprehensive hardware diagnostics 2 times
on this past Sunday and did tests especially on Memory like 4 time using the
Dell Diagnostics software and no errors were found.
Should I doubt the results and start changing the hardware components
gradually ?
Andrew J. Kelly wrote:
>The most likely cause of db integrity issues (especially recurring ones) is
>bad hardware. I would run some intensive hardware tests to find the root
>cause.
>> Hello,
>[quoted text clipped - 59 lines]
>> Sameer.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200511/1|||It still sounds like hardware related. Do you have a UPS and are you
confident of it's condition? But I just re-read your original post and
missed the part in which you were using Repair Allow data loss. That does
exactly what it says. So to fix the problems it has to destroy or loose
some data. The problem is that you don't know what data you loose and your
data integrity is not lost. Your best bet for a situation such as that is
to backup from the last known good backup. Since you are using simple mode
you can never do a restore to a point in time. That limits your restores to
the last full or differential backup. If you only do that once a night you
can loose up to 24 hours worth of work. You should rethink your backup
strategy. The fact that you have been doing this for some time now means
that you probably do not have a valid Full backup anymore. They most likely
all have some form of corruption in them. Either from what is causing the
issues or from you doing the repairs and allowing data loss. You might want
to consider creating a new db and copying the data out from one and back
into another with referential integrity constraints to see where you may
have bad data.
--
Andrew J. Kelly SQL MVP
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message
news:57db2f1476231@.uwe...
> Thanks Andrew,
> I forgot to mention that I did a comprehensive hardware diagnostics 2
> times
> on this past Sunday and did tests especially on Memory like 4 time using
> the
> Dell Diagnostics software and no errors were found.
> Should I doubt the results and start changing the hardware components
> gradually ?
>
> Andrew J. Kelly wrote:
>>The most likely cause of db integrity issues (especially recurring ones)
>>is
>>bad hardware. I would run some intensive hardware tests to find the root
>>cause.
>> Hello,
>>[quoted text clipped - 59 lines]
>> Sameer.
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200511/1|||Thanks Andrew,
1. I will check the UPS tomorrow and keep you posted. I'll also have the
batteries in the UPS replaced as soon as I can.
2. I do a backup every hour.
3. If I create a new database, should I use a different name or preferably
keep the same name as the current one with problems ? If I change to a new
name, that would add a lot of tasks for me to change the name wherever it
exists.....all codes, queries, reports, etc.
4. Given I create a new database, regardless of the issue in point 3 above,
how do I copy the data with referential integrity ? use DTS ? or queries ?
Thanks for your guidance....I highly appreciate it.
Sameer.
Andrew J. Kelly wrote:
>It still sounds like hardware related. Do you have a UPS and are you
>confident of it's condition? But I just re-read your original post and
>missed the part in which you were using Repair Allow data loss. That does
>exactly what it says. So to fix the problems it has to destroy or loose
>some data. The problem is that you don't know what data you loose and your
>data integrity is not lost. Your best bet for a situation such as that is
>to backup from the last known good backup. Since you are using simple mode
>you can never do a restore to a point in time. That limits your restores to
>the last full or differential backup. If you only do that once a night you
>can loose up to 24 hours worth of work. You should rethink your backup
>strategy. The fact that you have been doing this for some time now means
>that you probably do not have a valid Full backup anymore. They most likely
>all have some form of corruption in them. Either from what is causing the
>issues or from you doing the repairs and allowing data loss. You might want
>to consider creating a new db and copying the data out from one and back
>into another with referential integrity constraints to see where you may
>have bad data.
>> Thanks Andrew,
>[quoted text clipped - 17 lines]
>> Sameer.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200511/1|||3. The new db is just so that you can get the data in a know condition.
Once you have it where you are comfortable with it and want to use it in
production you can rename it after dropping the original.
4. What I meant was that if you have parent child relationships you want to
add RI constraints on the tables in the new db before you add the data.
That way you will know when you go to insert the data which rows are orphans
etc. It really wouldn't matter how you imported the data as long as you do
it in the right order. Parents first then children and so on.
Andrew J. Kelly SQL MVP
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message
news:57dfb788bfc8e@.uwe...
> Thanks Andrew,
> 1. I will check the UPS tomorrow and keep you posted. I'll also have the
> batteries in the UPS replaced as soon as I can.
> 2. I do a backup every hour.
> 3. If I create a new database, should I use a different name or preferably
> keep the same name as the current one with problems ? If I change to a new
> name, that would add a lot of tasks for me to change the name wherever it
> exists.....all codes, queries, reports, etc.
> 4. Given I create a new database, regardless of the issue in point 3
> above,
> how do I copy the data with referential integrity ? use DTS ? or queries ?
> Thanks for your guidance....I highly appreciate it.
> Sameer.
>
> Andrew J. Kelly wrote:
>>It still sounds like hardware related. Do you have a UPS and are you
>>confident of it's condition? But I just re-read your original post and
>>missed the part in which you were using Repair Allow data loss. That does
>>exactly what it says. So to fix the problems it has to destroy or loose
>>some data. The problem is that you don't know what data you loose and
>>your
>>data integrity is not lost. Your best bet for a situation such as that is
>>to backup from the last known good backup. Since you are using simple
>>mode
>>you can never do a restore to a point in time. That limits your restores
>>to
>>the last full or differential backup. If you only do that once a night
>>you
>>can loose up to 24 hours worth of work. You should rethink your backup
>>strategy. The fact that you have been doing this for some time now means
>>that you probably do not have a valid Full backup anymore. They most
>>likely
>>all have some form of corruption in them. Either from what is causing the
>>issues or from you doing the repairs and allowing data loss. You might
>>want
>>to consider creating a new db and copying the data out from one and back
>>into another with referential integrity constraints to see where you may
>>have bad data.
>> Thanks Andrew,
>>[quoted text clipped - 17 lines]
>> Sameer.
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200511/1|||Hi Andrew,
To give you latest status ...
1. I replaced the UPS batteries and after 4 days, corruption came back on one
table in the production database.
2. I also defragmented the disk and after a couple of days, corruption came
back.
3. My next step is to replace RAM chips and see what happens...
The weird thing is that when I get alerted through the DB Maintenance
Integrity Check failure, I run a DBCC CHECKDB and it does find errors.
However, when I simply stop/start the SQL Server, the error goes away WITHOUT
me even running a repair on that particular table.
Is there a way to flush all the connected users so that I can set the
database to a single user before repairing it ?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||> Is there a way to flush all the connected users so that I can set the
> database to a single user before repairing it ?
ALTER DATABASE with the ROLLBACK option.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message news:58622451c05f7@.uwe...
> Hi Andrew,
> To give you latest status ...
> 1. I replaced the UPS batteries and after 4 days, corruption came back on one
> table in the production database.
> 2. I also defragmented the disk and after a couple of days, corruption came
> back.
> 3. My next step is to replace RAM chips and see what happens...
> The weird thing is that when I get alerted through the DB Maintenance
> Integrity Check failure, I run a DBCC CHECKDB and it does find errors.
> However, when I simply stop/start the SQL Server, the error goes away WITHOUT
> me even running a repair on that particular table.
> Is there a way to flush all the connected users so that I can set the
> database to a single user before repairing it ?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||While the database is online and being used, I would like to stop all future
users from connecting from it, kill all current users logged-in and then
change the db to a single user mode to be repaired.
Could you please elaborate it more ?
Thanks.
--
Message posted via http://www.sqlmonster.com|||ALTER DATABASE dbname SET SINGLE_USER WITH ROILLBACK IMMEDIATE
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message news:5863a80856c4f@.uwe...
> While the database is online and being used, I would like to stop all future
> users from connecting from it, kill all current users logged-in and then
> change the db to a single user mode to be repaired.
> Could you please elaborate it more ?
> Thanks.
> --
> Message posted via http://www.sqlmonster.com|||Wow, it worked like a charm....
How do I reset it back to multi-user after I finish repairing it ?
Thanks a million.
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||ALTER DATABASE dbname SET MULTI_USER
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message news:5863d7195c667@.uwe...
> Wow, it worked like a charm....
> How do I reset it back to multi-user after I finish repairing it ?
> Thanks a million.
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||Thanks Mr. Karaszi ... I appreciate it !
Now only if this recurring Integrity errors would vanish away after I replace
the RAM, hopefully ....
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||You are not using a RAM disk by any chance are you?
--
Andrew J. Kelly SQL MVP
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message
news:58622451c05f7@.uwe...
> Hi Andrew,
> To give you latest status ...
> 1. I replaced the UPS batteries and after 4 days, corruption came back on
> one
> table in the production database.
> 2. I also defragmented the disk and after a couple of days, corruption
> came
> back.
> 3. My next step is to replace RAM chips and see what happens...
> The weird thing is that when I get alerted through the DB Maintenance
> Integrity Check failure, I run a DBCC CHECKDB and it does find errors.
> However, when I simply stop/start the SQL Server, the error goes away
> WITHOUT
> me even running a repair on that particular table.
> Is there a way to flush all the connected users so that I can set the
> database to a single user before repairing it ?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||Hi Andrew,
Thanks for coming back....what's a RAM disk ?
We're using a simple Primary Hard Disk being mirrored to a Secondary Hard
Disk using Windows Disk Mirroring functionality.
For Memory, we use 2 X 512 MB chips on 2 dimm slots.
Next plan is to buy 1 X 1GB memory chip and put it in 1 dimm slot and if need
be, buy another one and fill the last dimm slot.
--
Message posted via http://www.sqlmonster.com|||If you don't know then you are most likely not using it<g>. But you are
using software raid vs. hardware. I don't know if I would trust the
software mirroring. Maybe it's OK but that would be my guess. You might
want to look into a lug in card to do the mirroring.
--
Andrew J. Kelly SQL MVP
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message
news:58683e30c7369@.uwe...
> Hi Andrew,
> Thanks for coming back....what's a RAM disk ?
> We're using a simple Primary Hard Disk being mirrored to a Secondary Hard
> Disk using Windows Disk Mirroring functionality.
> For Memory, we use 2 X 512 MB chips on 2 dimm slots.
> Next plan is to buy 1 X 1GB memory chip and put it in 1 dimm slot and if
> need
> be, buy another one and fill the last dimm slot.
> --
> Message posted via http://www.sqlmonster.com|||1. Unfortunately, Hardware Mirroring is out of question for our small company,
atleast for now.
But just to verify if Software Mirroring is the cause, then I will
temporarily disable it and observe what happens.
2. I usually get corruptions in 2 tables (each are over half-a-million
records). I don't have any additional indexes in those tables apart from the
Primary Key [Id] column.
......2.1 Is it possible that indexes get corrupted for heavy tables ? If
so, how do I safely rebuild indexes
3. The 2 tables I mentioned above, each table gets populated by its own
corresponding Client VB App developed by one of the consultatnts we had hired.
However, even when I do inspect the code and design of the app, I don't seem
to find any flaws.
......3.1 Could those client apps causing the trouble ?
--
Message posted via SQLMonster.com
http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1|||It makes sense that the two most heavily used tables are the ones you see
the most issues with. Since they are changing more than the others there is
more opportunity for issues to arise. But the act of Inserting , Updating
and Deleting too much should not be a concern. Indexes don't get corrupted
after you reach a certain change threshold. I still think the hardware or
now maybe the mirroring software is the root cause. Hardware controllers
that do mirroring these days are extremely inexpensive. Most systems have
the capability built into the mother boards now. I think you will find it
is cheaper than you think and worth exploring.
--
Andrew J. Kelly SQL MVP
"Sameer via SQLMonster.com" <u4996@.uwe> wrote in message
news:586f11a2109af@.uwe...
> 1. Unfortunately, Hardware Mirroring is out of question for our small
> company,
> atleast for now.
> But just to verify if Software Mirroring is the cause, then I will
> temporarily disable it and observe what happens.
>
> 2. I usually get corruptions in 2 tables (each are over half-a-million
> records). I don't have any additional indexes in those tables apart from
> the
> Primary Key [Id] column.
> ......2.1 Is it possible that indexes get corrupted for heavy tables ?
> If
> so, how do I safely rebuild indexes
>
> 3. The 2 tables I mentioned above, each table gets populated by its own
> corresponding Client VB App developed by one of the consultatnts we had
> hired.
> However, even when I do inspect the code and design of the app, I don't
> seem
> to find any flaws.
> ......3.1 Could those client apps causing the trouble ?
> --
> Message posted via SQLMonster.com
> http://www.sqlmonster.com/Uwe/Forums.aspx/sql-server/200512/1

Friday, March 30, 2012

Internal Consistency Error, Restoring Backup

internal consistency error occurred while restoring a database

internal consistency error occurred while restoring a database

internal consistency error occurred while restoring a database

internal consistency error

internal consistency error

internal consistency error

internal consistency error

Wednesday, March 21, 2012

Interesting question

Interesting Maintenance Plan Problem

Interesting Maintenance Plan Problem

Interesting Maintenance Plan Problem

Wednesday, March 7, 2012

Integrity Check Failure

Integrity Check Failure

Integrity Check Failure

Integrity Check Errors

Integrity Check Errors

Integrity Check Errors

Integrated Security

Blog Archive

About Me