Run DBCC CHECKTABLE dbo.Employee. It may correct the problem or give you more info about it. If you want to get the best answer for your question read faq183-874 and thread183-468158. Terry L. Broadbent - DBA
SQL Server Page:
I tried DBCC CHECKTABLE but it does not help. Actually I got the message first when I ran DBCC CHECKDB and it returns the same error, which is on the primary key of the Employee table. I am trying to figure out how to do a repair on the primary key index of this table. I just want to drop it.
If the table contains no data, script it, drop it and create it anew. If you want to get the best answer for your question read faq183-874 and thread183-468158. Terry L. Broadbent - DBA
SQL Server Page:
Deleting the table is my last resort because there are lots of dependencies on the Employee table. I guess I will delete it if I can't figure out a way to repair it.
However, I can't delete the table even if I want to. I tried to drop it and the drop statement returned the same error message as the Alter Table statement shown in the first message of this thread.
Did you ever resolve this issue? Perhaps executing DBCC DBREINDEX would correct the problem. If you want to get the best answer for your question read faq183-874 and faq183-3179. Terry L. Broadbent - DBA
SQL Server Page:
DBCC CHECKTABLE ('Employee', REPAIR_REBUILD)
DBCC CHECKTABLE ('Employee', REPAIR_ALLOW_DATA_LOSS) If you want to get the best answer for your question read faq183-874 and faq183-3179. Terry L. Broadbent - DBA
SQL Server Page:
Can you add a row to the table or does that produce the same error? Which SQL Service service pack is installed?
You may have to drop the table. Make sure all the constraints are scripted. Disable constraints (such as foreign keyes) while you do drop and create the table. Procsedures and views that use the table should work after the table is recreated but you should recompile them.
I've run out of ideas. Hopefully, someone else can halp. You may need to contact Microsoft for help. If you want to get the best answer for your question read faq183-874 and faq183-3179. Terry L. Broadbent - DBA
SQL Server Page:
I can add rows but I cannot drop the table. I get the same doggone Connection Broken msg when I try to drop the table as I do when I try to drop the index. I think I have figured out what the problem is but I don't know how to fix it. I run this: dbcc checkdb ( 'WPBCTEST', REPAIR_ALLOW_DATA_LOSS) with NO_INFOMSGS
and I get this: Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 92821913600 owned by data record identified by RID = (1:134968:0) id = 1894206444 and indid = 3.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:1215), slot 1, text ID 92821913600 is referenced by page (1:134968), slot 0, but was not seen in the scan.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:96105), slot 1, text ID 92821913600 is not referenced.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
The repair level on the DBCC statement caused this repair to be bypassed.
CHECKDB found 0 allocation errors and 3 consistency errors in table 'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 3 consistency errors in database 'WPBCTEST'.
As I read this response, I think the server is saying that text ID 92821913600 is shown to be at page (1:1215), slot 1 but it is not there. Also, another text object text ID 92821913600, same id as the other object, is at page (1:96105), slot 1 but there is no reference to it. Apparently the reference to the text object got changed somehow and that is the problem. The question I have is how do I fix it?
I opened an email incident with Microsoft SQL Server Tech support but the response from them has been disappointing, to be kind. They promise a response withing 24 hours but I have had only two responses since I submitted the incident last Wednesday. And their explanations and solutions are so simple and elementary that they cannot be considered.
Sysindexes may be the real problem table. In the meantime, I'll do a little reasearch. If you want to get the best answer for your question read faq183-874 and faq183-3179. Terry L. Broadbent - DBA
SQL Server Page:
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.