Consistency errors/repair_all_data_loss question

I've been receiving consistency errors for the past few weeks
whenever the indexes on 1 table are rebuilt (which they are each
evening). I restored the production database to our development
server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
were the same (which would rule out hardware errors, right?)
DBREINDEX results:
A possible database consistency problem has been detected on database
'database_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on
database 'database_name'.
Connection Broken
Then I ran CHECKDB with repair_allow_data_loss (results below) and that
fixed the consistency errors (CHECKDB came back with no errors the
next time).
I read online (not BOL) that only index, header and consistency
information are removed with repair_all_data_loss, no actual data.
>From the info below, can you tell if the only thing that changed was
the clustered index? And if so, would it be safe (i.e., no data loss)
to run repair_allow_data_loss on the production database? I'd like
to clean this error up without resorting to a month old backup, which
would definitely mean data loss.
Thanks!!
CHECKDB with repair_allow_data_loss results:
CHECKDB found 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
Ran DBCC CHECKDB ('database_name',repair_allow_data_loss) WITH
ALL_ERRORMSGS
DBCC results for 'dbowner.f8'.
Server: Msg 8944, Level 16, State 4, Line 1
Table error: Object ID 1648724926, index ID 0, page (1:155093), row 25.
Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1648724926, index ID 1. Page (1:155093) was not
seen in the scan although its parent (1:155073) and previous (1:155092)
refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1648724926, index ID 1. Page (1:155094) is
missing a reference from previous page (1:155093). Possible chain
linkage problem.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 10, text ID 41680896 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 11, text ID 1340932096 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 12, text ID 23986176 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313604), slot 0, text ID 96010240 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313604), slot 1, text ID 817430528 is not referenced.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Repair: Page (1:155093) has been deallocated from object ID 1648724926,
index ID 0.
Clustered index successfully restored for object 'dbowner.f8' in
database 'database_name'.
There are 1140058 rows in 33131 pages for object 'dbowner.f8'.
CHECKDB found 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
CHECKDB fixed 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
Select count (*) from dbowner.f8 on development server shows: 1140058
Select count (*) from dbowner.f8 on production server shows: 1145787
> I restored the production database to our development
> server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
> were the same (which would rule out hardware errors, right?)
I doubt it will rule out hw errors. I can imagine that hw errors were introduced on the prod
machine, corrupted the db and is carried over by your backup on the test machine.

> I read online (not BOL) that only index, header and consistency
> information are removed with repair_all_data_loss, no actual data.
Que! Can you post that link? AFAIK, The option does what it say. If will remove all corrupted pages,
resulting in possible data loss. In your case, you seem to have problems in index 0 (a data page)
for a user object (just reading the first error you posted). That page will be removed = data loss.
I strongly encourage you to open a case with MS Support, assuming that you value the database > the
few hundred bucks a support issue costs. They might not be able to help you further, but you have
tried. And make sure you do far more frequent CHECKDBs. Also, you might want to check
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/
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1127328673.857606.24480@.f14g2000cwb.googlegro ups.com...
> I've been receiving consistency errors for the past few weeks
> whenever the indexes on 1 table are rebuilt (which they are each
> evening). I restored the production database to our development
> server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
> were the same (which would rule out hardware errors, right?)
> DBREINDEX results:
> A possible database consistency problem has been detected on database
> 'database_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on
> database 'database_name'.
> Connection Broken
>
> Then I ran CHECKDB with repair_allow_data_loss (results below) and that
> fixed the consistency errors (CHECKDB came back with no errors the
> next time).
> I read online (not BOL) that only index, header and consistency
> information are removed with repair_all_data_loss, no actual data.
> the clustered index? And if so, would it be safe (i.e., no data loss)
> to run repair_allow_data_loss on the production database? I'd like
> to clean this error up without resorting to a month old backup, which
> would definitely mean data loss.
> Thanks!!
> CHECKDB with repair_allow_data_loss results:
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> Ran DBCC CHECKDB ('database_name',repair_allow_data_loss) WITH
> ALL_ERRORMSGS
> DBCC results for 'dbowner.f8'.
> Server: Msg 8944, Level 16, State 4, Line 1
> Table error: Object ID 1648724926, index ID 0, page (1:155093), row 25.
> Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1648724926, index ID 1. Page (1:155093) was not
> seen in the scan although its parent (1:155073) and previous (1:155092)
> refer to it. Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1648724926, index ID 1. Page (1:155094) is
> missing a reference from previous page (1:155093). Possible chain
> linkage problem.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 10, text ID 41680896 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 11, text ID 1340932096 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 12, text ID 23986176 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313604), slot 0, text ID 96010240 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313604), slot 1, text ID 817430528 is not referenced.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> Repair: Page (1:155093) has been deallocated from object ID 1648724926,
> index ID 0.
> Clustered index successfully restored for object 'dbowner.f8' in
> database 'database_name'.
> There are 1140058 rows in 33131 pages for object 'dbowner.f8'.
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> CHECKDB fixed 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> Select count (*) from dbowner.f8 on development server shows: 1140058
> Select count (*) from dbowner.f8 on production server shows: 1145787
>

Consistency errors/repair_all_data_loss question

I've been receiving consistency errors for the past few weeks
whenever the indexes on 1 table are rebuilt (which they are each
evening). I restored the production database to our development
server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
were the same (which would rule out hardware errors, right?)
DBREINDEX results:
A possible database consistency problem has been detected on database
'database_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on
database 'database_name'.
Connection Broken
Then I ran CHECKDB with repair_allow_data_loss (results below) and that
fixed the consistency errors (CHECKDB came back with no errors the
next time).
I read online (not BOL) that only index, header and consistency
information are removed with repair_all_data_loss, no actual data.
>From the info below, can you tell if the only thing that changed was
the clustered index? And if so, would it be safe (i.e., no data loss)
to run repair_allow_data_loss on the production database? I'd like
to clean this error up without resorting to a month old backup, which
would definitely mean data loss.
Thanks!!
CHECKDB with repair_allow_data_loss results:
CHECKDB found 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
Ran DBCC CHECKDB ('database_name',repair_allow_data_loss) WITH
ALL_ERRORMSGS
DBCC results for 'dbowner.f8'.
Server: Msg 8944, Level 16, State 4, Line 1
Table error: Object ID 1648724926, index ID 0, page (1:155093), row 25.
Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1648724926, index ID 1. Page (1:155093) was not
seen in the scan although its parent (1:155073) and previous (1:155092)
refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1648724926, index ID 1. Page (1:155094) is
missing a reference from previous page (1:155093). Possible chain
linkage problem.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 10, text ID 41680896 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 11, text ID 1340932096 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 12, text ID 23986176 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313604), slot 0, text ID 96010240 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313604), slot 1, text ID 817430528 is not referenced.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Repair: Page (1:155093) has been deallocated from object ID 1648724926,
index ID 0.
Clustered index successfully restored for object 'dbowner.f8' in
database 'database_name'.
There are 1140058 rows in 33131 pages for object 'dbowner.f8'.
CHECKDB found 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
CHECKDB fixed 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
Select count (*) from dbowner.f8 on development server shows: 1140058
Select count (*) from dbowner.f8 on production server shows: 1145787> I restored the production database to our development
> server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
> were the same (which would rule out hardware errors, right?)
I doubt it will rule out hw errors. I can imagine that hw errors were introduced on the prod
machine, corrupted the db and is carried over by your backup on the test machine.
> I read online (not BOL) that only index, header and consistency
> information are removed with repair_all_data_loss, no actual data.
Que! Can you post that link? AFAIK, The option does what it say. If will remove all corrupted pages,
resulting in possible data loss. In your case, you seem to have problems in index 0 (a data page)
for a user object (just reading the first error you posted). That page will be removed = data loss.
I strongly encourage you to open a case with MS Support, assuming that you value the database > the
few hundred bucks a support issue costs. They might not be able to help you further, but you have
tried. And make sure you do far more frequent CHECKDBs. Also, you might want to check
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/
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1127328673.857606.24480@.f14g2000cwb.googlegroups.com...
> I've been receiving consistency errors for the past few weeks
> whenever the indexes on 1 table are rebuilt (which they are each
> evening). I restored the production database to our development
> server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
> were the same (which would rule out hardware errors, right?)
> DBREINDEX results:
> A possible database consistency problem has been detected on database
> 'database_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on
> database 'database_name'.
> Connection Broken
>
> Then I ran CHECKDB with repair_allow_data_loss (results below) and that
> fixed the consistency errors (CHECKDB came back with no errors the
> next time).
> I read online (not BOL) that only index, header and consistency
> information are removed with repair_all_data_loss, no actual data.
>>From the info below, can you tell if the only thing that changed was
> the clustered index? And if so, would it be safe (i.e., no data loss)
> to run repair_allow_data_loss on the production database? I'd like
> to clean this error up without resorting to a month old backup, which
> would definitely mean data loss.
> Thanks!!
> CHECKDB with repair_allow_data_loss results:
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> Ran DBCC CHECKDB ('database_name',repair_allow_data_loss) WITH
> ALL_ERRORMSGS
> DBCC results for 'dbowner.f8'.
> Server: Msg 8944, Level 16, State 4, Line 1
> Table error: Object ID 1648724926, index ID 0, page (1:155093), row 25.
> Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1648724926, index ID 1. Page (1:155093) was not
> seen in the scan although its parent (1:155073) and previous (1:155092)
> refer to it. Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1648724926, index ID 1. Page (1:155094) is
> missing a reference from previous page (1:155093). Possible chain
> linkage problem.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 10, text ID 41680896 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 11, text ID 1340932096 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 12, text ID 23986176 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313604), slot 0, text ID 96010240 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313604), slot 1, text ID 817430528 is not referenced.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> Repair: Page (1:155093) has been deallocated from object ID 1648724926,
> index ID 0.
> Clustered index successfully restored for object 'dbowner.f8' in
> database 'database_name'.
> There are 1140058 rows in 33131 pages for object 'dbowner.f8'.
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> CHECKDB fixed 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> Select count (*) from dbowner.f8 on development server shows: 1140058
> Select count (*) from dbowner.f8 on production server shows: 1145787
>

Consistency errors/repair_all_data_loss question

I've been receiving consistency errors for the past few weeks
whenever the indexes on 1 table are rebuilt (which they are each
evening). I restored the production database to our development
server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
were the same (which would rule out hardware errors, right?)
DBREINDEX results:
A possible database consistency problem has been detected on database
'database_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on
database 'database_name'.
Connection Broken
Then I ran CHECKDB with repair_allow_data_loss (results below) and that
fixed the consistency errors (CHECKDB came back with no errors the
next time).
I read online (not BOL) that only index, header and consistency
information are removed with repair_all_data_loss, no actual data.
>From the info below, can you tell if the only thing that changed was
the clustered index? And if so, would it be safe (i.e., no data loss)
to run repair_allow_data_loss on the production database? I'd like
to clean this error up without resorting to a month old backup, which
would definitely mean data loss.
Thanks!!
CHECKDB with repair_allow_data_loss results:
CHECKDB found 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
Ran DBCC CHECKDB ('database_name',repair_allow_data_loss)
WITH
ALL_ERRORMSGS
DBCC results for 'dbowner.f8'.
Server: Msg 8944, Level 16, State 4, Line 1
Table error: Object ID 1648724926, index ID 0, page (1:155093), row 25.
Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
Server: Msg 8976, Level 16, State 1, Line 1
Table error: Object ID 1648724926, index ID 1. Page (1:155093) was not
seen in the scan although its parent (1:155073) and previous (1:155092)
refer to it. Check any previous errors.
Server: Msg 8978, Level 16, State 1, Line 1
Table error: Object ID 1648724926, index ID 1. Page (1:155094) is
missing a reference from previous page (1:155093). Possible chain
linkage problem.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 10, text ID 41680896 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 11, text ID 1340932096 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313603), slot 12, text ID 23986176 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313604), slot 0, text ID 96010240 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 1648724926. The text, ntext, or image node at
page (1:313604), slot 1, text ID 817430528 is not referenced.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
The error has been repaired.
Repair: Page (1:155093) has been deallocated from object ID 1648724926,
index ID 0.
Clustered index successfully restored for object 'dbowner.f8' in
database 'database_name'.
There are 1140058 rows in 33131 pages for object 'dbowner.f8'.
CHECKDB found 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
CHECKDB fixed 0 allocation errors and 9 consistency errors in table
'dbowner.f8' (object ID 1648724926).
Select count (*) from dbowner.f8 on development server shows: 1140058
Select count (*) from dbowner.f8 on production server shows: 1145787> I restored the production database to our development
> server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
> were the same (which would rule out hardware errors, right?)
I doubt it will rule out hw errors. I can imagine that hw errors were introd
uced on the prod
machine, corrupted the db and is carried over by your backup on the test mac
hine.

> I read online (not BOL) that only index, header and consistency
> information are removed with repair_all_data_loss, no actual data.
Que! Can you post that link? AFAIK, The option does what it say. If will rem
ove all corrupted pages,
resulting in possible data loss. In your case, you seem to have problems in
index 0 (a data page)
for a user object (just reading the first error you posted). That page will
be removed = data loss.
I strongly encourage you to open a case with MS Support, assuming that you v
alue the database > the
few hundred bucks a support issue costs. They might not be able to help you
further, but you have
tried. And make sure you do far more frequent CHECKDBs. Also, you might want
to check
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/
"nmsm" <naomimsm@.gmail.com> wrote in message
news:1127328673.857606.24480@.f14g2000cwb.googlegroups.com...
> I've been receiving consistency errors for the past few weeks
> whenever the indexes on 1 table are rebuilt (which they are each
> evening). I restored the production database to our development
> server and ran DBCC CHECKDB and DBREINDEX to confirm that the errors
> were the same (which would rule out hardware errors, right?)
> DBREINDEX results:
> A possible database consistency problem has been detected on database
> 'database_name'. DBCC CHECKDB and DBCC CHECKCATALOG should be run on
> database 'database_name'.
> Connection Broken
>
> Then I ran CHECKDB with repair_allow_data_loss (results below) and that
> fixed the consistency errors (CHECKDB came back with no errors the
> next time).
> I read online (not BOL) that only index, header and consistency
> information are removed with repair_all_data_loss, no actual data.
> the clustered index? And if so, would it be safe (i.e., no data loss)
> to run repair_allow_data_loss on the production database? I'd like
> to clean this error up without resorting to a month old backup, which
> would definitely mean data loss.
> Thanks!!
> CHECKDB with repair_allow_data_loss results:
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> Ran DBCC CHECKDB ('database_name',repair_allow_data_loss)
WITH
> ALL_ERRORMSGS
> DBCC results for 'dbowner.f8'.
> Server: Msg 8944, Level 16, State 4, Line 1
> Table error: Object ID 1648724926, index ID 0, page (1:155093), row 25.
> Test (offsetNull >= BASEOFFSET) failed. Values are 0 and 4.
> Server: Msg 8976, Level 16, State 1, Line 1
> Table error: Object ID 1648724926, index ID 1. Page (1:155093) was not
> seen in the scan although its parent (1:155073) and previous (1:155092)
> refer to it. Check any previous errors.
> Server: Msg 8978, Level 16, State 1, Line 1
> Table error: Object ID 1648724926, index ID 1. Page (1:155094) is
> missing a reference from previous page (1:155093). Possible chain
> linkage problem.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 10, text ID 41680896 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 11, text ID 1340932096 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313603), slot 12, text ID 23986176 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313604), slot 0, text ID 96010240 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 1648724926. The text, ntext, or image node at
> page (1:313604), slot 1, text ID 817430528 is not referenced.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> The error has been repaired.
> Repair: Page (1:155093) has been deallocated from object ID 1648724926,
> index ID 0.
> Clustered index successfully restored for object 'dbowner.f8' in
> database 'database_name'.
> There are 1140058 rows in 33131 pages for object 'dbowner.f8'.
> CHECKDB found 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> CHECKDB fixed 0 allocation errors and 9 consistency errors in table
> 'dbowner.f8' (object ID 1648724926).
> Select count (*) from dbowner.f8 on development server shows: 1140058
> Select count (*) from dbowner.f8 on production server shows: 1145787
>sqlsql

Connectivity problem-please read

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing,
however when i checked the event logs on all servers,
there is no error message there. all different messages
include a "General network error" for example one of them
is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobHi Rob,
10054 is usually seen when the underlying tcp session is dropped. The
only way to tshoot this is to make network traces from the client capturing
the problem. Then work with your network staff to resolve them. More than
likely, the cause is a dropped tcp session.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
Can you explain a bit more, How can I make the Network
trace? Basically, I can not see any problem with the
network, what kind of network problems should I looking
for?
Thanks a lot-Rob
>--Original Message--
>Hi Rob,
> 10054 is usually seen when the underlying tcp session
is dropped. The
>only way to tshoot this is to make network traces from
the client capturing
>the problem. Then work with your network staff to
resolve them. More than
>likely, the cause is a dropped tcp session.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>|||Hi Rob,
So all SQL connections from clients are supported by underlying tcp or
smb sessions. ODBC and OLEdb applications rely on the integrity of the
underlying network session. If the session is torn down, then the
application will fail. In our case we tend to report "general network
Error".
So, if this is the error you're seeing, you need to make network traces
from the client and see if the underlying tcp or smb session was dropped.
Then work with your network team to resolve it.
Otherwise, you can make the traces and open a case with us to help do the
review.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sqlsql

Connectivity problem-please read

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing,
however when i checked the event logs on all servers,
there is no error message there. all different messages
include a "General network error" for example one of them
is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-Rob
Hi Rob,
10054 is usually seen when the underlying tcp session is dropped. The
only way to tshoot this is to make network traces from the client capturing
the problem. Then work with your network staff to resolve them. More than
likely, the cause is a dropped tcp session.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi Kevin,
Can you explain a bit more, How can I make the Network
trace? Basically, I can not see any problem with the
network, what kind of network problems should I looking
for?
Thanks a lot-Rob
>--Original Message--
>Hi Rob,
> 10054 is usually seen when the underlying tcp session
is dropped. The
>only way to tshoot this is to make network traces from
the client capturing
>the problem. Then work with your network staff to
resolve them. More than
>likely, the cause is a dropped tcp session.
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
>
>.
>
|||Hi Rob,
So all SQL connections from clients are supported by underlying tcp or
smb sessions. ODBC and OLEdb applications rely on the integrity of the
underlying network session. If the session is torn down, then the
application will fail. In our case we tend to report "general network
Error".
So, if this is the error you're seeing, you need to make network traces
from the client and see if the underlying tcp or smb session was dropped.
Then work with your network team to resolve it.
Otherwise, you can make the traces and open a case with us to help do the
review.
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobAre the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob

>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
the[vbcol=seagreen]
there[vbcol=seagreen]
include[vbcol=seagreen]
to[vbcol=seagreen]
problem, I[vbcol=seagreen]
have[vbcol=seagreen]
>
>.
>|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/defaul...d=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!sqlsql

Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-RobAre the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob
>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
>> Hi,
>> I have 3 SQL servers 7, and since yesterday, some of my
>> clients started receiving different error messages in
the
>> middle of doing something like reporting, or editing.
>> (they run different applications).
>> However when i checked the event logs on all servers
there
>> is no error message there. all different messages
include
>> a "General network error" for example one of them is:
>> SQL Server Message 10054, Possible network error Write
to
>> SQL Server Failed. General Network Error. Check your
>> documentation. Debugging info: sqlCompile...
>> Usually if I reboot their WS, thats temperary fixs their
>> problem.
>> Does anyone have any idea how to deal with this
problem, I
>> am monitoring different switches but cannot see any
>> problem. Also checked ODBC settings all fine, and we
have
>> these setting for a couple of years with no problem.
>> Thanks in advance for any help-Rob
>>
>
>.
>|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/default.aspx?scid=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
---
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Connectivity problem

Hi,
I have 3 SQL servers 7, and since yesterday, some of my
clients started receiving different error messages in the
middle of doing something like reporting, or editing.
(they run different applications).
However when i checked the event logs on all servers there
is no error message there. all different messages include
a "General network error" for example one of them is:
SQL Server Message 10054, Possible network error Write to
SQL Server Failed. General Network Error. Check your
documentation. Debugging info: sqlCompile...
Usually if I reboot their WS, thats temperary fixs their
problem.
Does anyone have any idea how to deal with this problem, I
am monitoring different switches but cannot see any
problem. Also checked ODBC settings all fine, and we have
these setting for a couple of years with no problem.
Thanks in advance for any help-Rob
Are the errors occurring on all 3 SQL Servers or just one SQL Server?
How is the health of the network? Are the switches in good working order?
How about the NIC's in the SQL Server machines? Is your DNS acting up?
What service packs have you applied recently to any equipment in the process
(Client, Server, routers/switches etc.).
What has changed in the last few weeks?
Rick Sawtell
MCT, MCSD, MCDBA
"Rob" <Rob@.nul.ca> wrote in message
news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
> Hi,
> I have 3 SQL servers 7, and since yesterday, some of my
> clients started receiving different error messages in the
> middle of doing something like reporting, or editing.
> (they run different applications).
> However when i checked the event logs on all servers there
> is no error message there. all different messages include
> a "General network error" for example one of them is:
> SQL Server Message 10054, Possible network error Write to
> SQL Server Failed. General Network Error. Check your
> documentation. Debugging info: sqlCompile...
> Usually if I reboot their WS, thats temperary fixs their
> problem.
> Does anyone have any idea how to deal with this problem, I
> am monitoring different switches but cannot see any
> problem. Also checked ODBC settings all fine, and we have
> these setting for a couple of years with no problem.
> Thanks in advance for any help-Rob
>
|||On 2 of them. The network health is good and I can not see
any problem. As long as I am aware, we havent changed
anything recently and this problem startd since a couple
days ago.
Rob

>--Original Message--
>Are the errors occurring on all 3 SQL Servers or just one
SQL Server?
>How is the health of the network? Are the switches in
good working order?
>How about the NIC's in the SQL Server machines? Is your
DNS acting up?
>What service packs have you applied recently to any
equipment in the process[vbcol=seagreen]
>(Client, Server, routers/switches etc.).
>What has changed in the last few weeks?
>
>Rick Sawtell
>MCT, MCSD, MCDBA
>
>
>"Rob" <Rob@.nul.ca> wrote in message
>news:d37d01c48ab6$39d66790$a601280a@.phx.gbl...
the[vbcol=seagreen]
there[vbcol=seagreen]
include[vbcol=seagreen]
to[vbcol=seagreen]
problem, I[vbcol=seagreen]
have
>
>.
>
|||Hi Bob,
Thanks for using MSDN Managed Newsgroup!
From your descriptions, I understood that your SQL7 received different
error and General Network Error. Have I understood you? If their is
anything I misunderstood, please feel free to let me know.
First of all, Would you please show me a detailed descriptions of what kind
of error message it will show? Is it possible for you to paste your latest
error log here?
Secondly, based on my scope, "General network error" doesn't mean a network
issue in most cases, it is a very common error that I am afraid we need
more time troubleshooting.
Thirdly, you said it will temperarily fix the problem by rebooting. How
long after rebooting will this kind of error occurs again?
Last but not the least, if it is an urgent one, you can contact Microsoft
Product Support directly to discuss additional support options you may have
available, by contacting us at 1-(800)936-5800 or by choosing one of the
options listed at
http://support.microsoft.com/default...=sz;en-us;top.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Mingqing Cheng
Microsoft Developer Community Support
Introduction to Yukon! - http://www.microsoft.com/sql/yukon
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks!

Connection problem

I have a multi-user web environment and amoccassionally receiving the following error msg with our SQL Server 2005 db:

A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)

I know there are numerous posts about this, but there doesn't seem to be a definitive "fix" for the issue after looking at the posts.

I am using the "WITH (NOLOCK)" option on some of the tables within my stored procedures. I need this option for certain tables I am accessing.

My ConnectionstringTimeout property is set for 45 seconds and my CommandTimeout property is set for 150 seconds.

Could a MS DBA please look into this issueASAP and get back with a definitive resolution?

btw, I am also using Connection Pooling with a min size of 2 and max size of 200.

Can someone please reply back who knows a definitive resolution to this problem?

|||

Hi wsyeager,

Well, seems thre is no ms dba answer your question here so i would try to deliver some effort. I searched through google and found this information. It makes sense to me

guess the problem is the connection pool. Recall that when you close
a connection from your .Net app, the connection to SQL Server is not
really closed. Instead ADO .Net lingers to it, for another 60 seconds,
and if the applicaiton opens a new connection during this time, it will
reuse the connection.

When you issue ALTER DATABASE WITH ROLLBACK IMMEDIATE, SQL Server will
terminate these connections. However, this is not something that ADO .Net
can detect. So it gives you a connection which it thinks is good, but
which isn't.

There are a couple of ways to approach this. One is to configure the
connection pool, so that all connections are dropped when you drop the
database. Another is to change the connection string, each time you
drop the database, as different connection strings gives different pools.

I would suggest that the best way, though, is simply to set up an exception
handler, so that you simply trap this error, and then try to reconnect.

See original artilce at:http://www.msdner.com/forum/thread476823.html

I sincerely hope it can help

|||

Bo, thanks a lot!

I simply look for that exception number (10054) in my middle tier object and retry the cmd again and it works fine now.