data corruption question

sql2k sp3
Based on recent experience Ive got a few questions about data corruption:
1> How does it happen?
2> What can be done to prevent it?
3> If it does happen, what are the proper steps to try to fix it without
restoring?
4> If I do need to restore, how do I know how far back to restore? I wouldnt
want to go through a lengthy restore process and then find out I still have
the corruption. Is there a way to know the day/time it first started?
TIA, ChrisRHi
99.999% of all corruption is caused by hardware.
Get good and reputable hardware and don't cut corners when installing it.
Have a UPS to keep the server up during power interruptions. Have battery
backed up RAID controller cards.
Make very regular backups, including transaction logs and get them off to
tape ASAP. Run regular DBCC's to check the consistency of the databases, and
have 'Torn page detection' on for each database. This will tell you very
quickly that some corruption has occurred. How often? Well, depending on
your uptime requirements, DBCC's daily does not sound like a bad idea.
Some times, corruption is not detected until weeks after it occurred so you
loose a lot. Daily, at worst case you loose a day's data.
Run the latest BIOS and driver versions, keep up to date with Windows SP's
and hotfixes and SQL SP's.
Don't plug you server and the kettle into the same wall plug, and keep the
Managers away from the servers. LOL.
Most of it is just common sense.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1A640B78-E981-4F57-B8A9-AF324C0ECE10@.microsoft.com...
> sql2k sp3
> Based on recent experience Ive got a few questions about data corruption:
> 1> How does it happen?
> 2> What can be done to prevent it?
> 3> If it does happen, what are the proper steps to try to fix it without
> restoring?
> 4> If I do need to restore, how do I know how far back to restore? I
wouldnt
> want to go through a lengthy restore process and then find out I still
have
> the corruption. Is there a way to know the day/time it first started?
> TIA, ChrisR

data corruption question

sql2k sp3
Based on recent experience Ive got a few questions about data corruption:
1> How does it happen?
2> What can be done to prevent it?
3> If it does happen, what are the proper steps to try to fix it without
restoring?
4> If I do need to restore, how do I know how far back to restore? I wouldnt
want to go through a lengthy restore process and then find out I still have
the corruption. Is there a way to know the day/time it first started?
TIA, ChrisR
Hi
99.999% of all corruption is caused by hardware.
Get good and reputable hardware and don't cut corners when installing it.
Have a UPS to keep the server up during power interruptions. Have battery
backed up RAID controller cards.
Make very regular backups, including transaction logs and get them off to
tape ASAP. Run regular DBCC's to check the consistency of the databases, and
have 'Torn page detection' on for each database. This will tell you very
quickly that some corruption has occurred. How often? Well, depending on
your uptime requirements, DBCC's daily does not sound like a bad idea.
Some times, corruption is not detected until weeks after it occurred so you
loose a lot. Daily, at worst case you loose a day's data.
Run the latest BIOS and driver versions, keep up to date with Windows SP's
and hotfixes and SQL SP's.
Don't plug you server and the kettle into the same wall plug, and keep the
Managers away from the servers. LOL.
Most of it is just common sense.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1A640B78-E981-4F57-B8A9-AF324C0ECE10@.microsoft.com...
> sql2k sp3
> Based on recent experience Ive got a few questions about data corruption:
> 1> How does it happen?
> 2> What can be done to prevent it?
> 3> If it does happen, what are the proper steps to try to fix it without
> restoring?
> 4> If I do need to restore, how do I know how far back to restore? I
wouldnt
> want to go through a lengthy restore process and then find out I still
have
> the corruption. Is there a way to know the day/time it first started?
> TIA, ChrisR

data corruption question

sql2k sp3
Based on recent experience Ive got a few questions about data corruption:
1> How does it happen?
2> What can be done to prevent it?
3> If it does happen, what are the proper steps to try to fix it without
restoring?
4> If I do need to restore, how do I know how far back to restore? I wouldnt
want to go through a lengthy restore process and then find out I still have
the corruption. Is there a way to know the day/time it first started?
TIA, ChrisRHi
99.999% of all corruption is caused by hardware.
Get good and reputable hardware and don't cut corners when installing it.
Have a UPS to keep the server up during power interruptions. Have battery
backed up RAID controller cards.
Make very regular backups, including transaction logs and get them off to
tape ASAP. Run regular DBCC's to check the consistency of the databases, and
have 'Torn page detection' on for each database. This will tell you very
quickly that some corruption has occurred. How often? Well, depending on
your uptime requirements, DBCC's daily does not sound like a bad idea.
Some times, corruption is not detected until weeks after it occurred so you
loose a lot. Daily, at worst case you loose a day's data.
Run the latest BIOS and driver versions, keep up to date with Windows SP's
and hotfixes and SQL SP's.
Don't plug you server and the kettle into the same wall plug, and keep the
Managers away from the servers. LOL.
Most of it is just common sense.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:1A640B78-E981-4F57-B8A9-AF324C0ECE10@.microsoft.com...
> sql2k sp3
> Based on recent experience Ive got a few questions about data corruption:
> 1> How does it happen?
> 2> What can be done to prevent it?
> 3> If it does happen, what are the proper steps to try to fix it without
> restoring?
> 4> If I do need to restore, how do I know how far back to restore? I
wouldnt
> want to go through a lengthy restore process and then find out I still
have
> the corruption. Is there a way to know the day/time it first started?
> TIA, ChrisR

Data corruption on a replicated database

We are running SQL 2000 EI SP3 on a Windows 2000 Adv. Server
We have recently setup a database for replication using transactional replication every ten minutes
Shortly after implementing this, we started receiving integrity errors on the database on a daily basis
Many of the errors are requiring checktable with repair data loss to correct the problem. The corruption has shown up on both replicated and non-replicated tables, but only occurs if replication is running. As soon as replication was stopped, the database quit reporting integrity errors
Please let me know if you need further information
Has anyone else ran into this?I don't think replication has anything to do with it. Probably replication
is stressing your hard disk subsystem, leading to errors. So the real
culprit could be hardware. Check your event viewer and any hardware logs for
clues.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ghost" <anonymous@.discussions.microsoft.com> wrote in message
news:B6B0118A-C15D-41A5-9E11-FA01F4AD14BD@.microsoft.com...
We are running SQL 2000 EI SP3 on a Windows 2000 Adv. Server.
We have recently setup a database for replication using transactional
replication every ten minutes.
Shortly after implementing this, we started receiving integrity errors on
the database on a daily basis.
Many of the errors are requiring checktable with repair data loss to correct
the problem. The corruption has shown up on both replicated and
non-replicated tables, but only occurs if replication is running. As soon
as replication was stopped, the database quit reporting integrity errors.
Please let me know if you need further information.
Has anyone else ran into this?|||Our first thought was hardware as well, however, a few things are pointing to something else causing the problem
1. All of the hardware is brand new, and the server is running at about a quarter of our target performance. (This server is not yet hosting databases that will be added later this year... During peak time we are seeing a max utilization of 15% across all processors). The hardware vendor has already been over this server and hasn't found anything, and there is no hardware related errors in the server event log
2. This is the first enterprise class server we have run in a SAN environment. To eliminate the SAN hardware or network we moved all of the data to internal drives on the server. The problem continues to occur
3. This server is hosting multiple application databases. The only database with errors is the replicated database. If this was hardware related we would expect to see the other databases having problems, as they were using the same internal hardware and SAN array to hold their data as the replicated database
Any thoughts|||Okay, could you post the exact errors you are seeing in the SQL Server error
logs?
Are you replicating text or image columns?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ghost" <anonymous@.discussions.microsoft.com> wrote in message
news:34BB1D32-6935-40A8-B061-1372260A868B@.microsoft.com...
Our first thought was hardware as well, however, a few things are pointing
to something else causing the problem:
1. All of the hardware is brand new, and the server is running at about a
quarter of our target performance. (This server is not yet hosting databases
that will be added later this year... During peak time we are seeing a max
utilization of 15% across all processors). The hardware vendor has already
been over this server and hasn't found anything, and there is no hardware
related errors in the server event logs
2. This is the first enterprise class server we have run in a SAN
environment. To eliminate the SAN hardware or network we moved all of the
data to internal drives on the server. The problem continues to occur.
3. This server is hosting multiple application databases. The only
database with errors is the replicated database. If this was hardware
related we would expect to see the other databases having problems, as they
were using the same internal hardware and SAN array to hold their data as
the replicated database.
Any thoughts?|||Yes, There are both image and text columns in some of the tables
Below is excerpt from the maintenance log on the errors we are getting
[1] Database ServiceCenter: Check Data and Index Linkage..
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8929: [Microsoft][ODBC SQL Server Driver][SQL Server]Object ID 525244926: Errors found in text ID 462078345216 owned by data record identified by RID = (1:202550:3)
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 525244926. The text, ntext, or image node at page (1:40468), slot 12, text ID 462078345216 is referenced by page (1:202550), slot 3, but was not seen in the scan
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 525244926. The text, ntext, or image node at page (1:695828), slot 12, text ID 462078345216 is not referenced
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Database 'ServiceCenter', index 'applicationm1.applicationm1_P' (ID 1589580701) (index ID 2). Extra or invalid key for the keys
[Microsoft][ODBC SQL Server Driver][SQL Server]Index row (1:81744:140) with values (application = 'cc.find.problem' and label = 'build.s) points to the data row identified by (RID = (1:348126:8))
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3 consistency errors in table 'problemm1' (object ID 525244926)
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1 consistency errors in table 'applicationm1' (object ID 1589580701)
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 4 consistency errors in database 'ServiceCenter'
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (ServiceCenter ).|||There are a lot of bugs/problems, replicating text/image columns. First make
sure all participating servers are on the latest service pack. Then see if
you find any hits for those error numbers at: http://support.microsoft.com
And consider contacting Microsoft support.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ghost" <anonymous@.discussions.microsoft.com> wrote in message
news:07926FA4-64B3-4038-8934-E2A3A631DDE3@.microsoft.com...
Yes, There are both image and text columns in some of the tables.
Below is excerpt from the maintenance log on the errors we are getting:
[1] Database ServiceCenter: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8929: [Microsoft][ODBC SQL
Server Driver][SQL Server]Object ID 525244926: Errors found in text ID
462078345216 owned by data record identified by RID = (1:202550:3).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
525244926. The text, ntext, or image node at page (1:40468), slot 12, text
ID 462078345216 is referenced by page (1:202550), slot 3, but was not seen
in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
525244926. The text, ntext, or image node at page (1:695828), slot 12, text
ID 462078345216 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Database
'ServiceCenter', index 'applicationm1.applicationm1_P' (ID 1589580701)
(index ID 2). Extra or invalid key for the keys:
[Microsoft][ODBC SQL Server Driver][SQL Server]Index row (1:81744:140) with
values (application = 'cc.find.problem' and label = 'build.s) points to the
data row identified by (RID = (1:348126:8)).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 3 consistency errors in table 'problemm1' (object ID 525244926).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 1 consistency errors in table 'applicationm1' (object ID
1589580701).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 4 consistency errors in database 'ServiceCenter'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (ServiceCenter ).

Data corruption on a replicated database

We are running SQL 2000 EI SP3 on a Windows 2000 Adv. Server.
We have recently setup a database for replication using transactional replic
ation every ten minutes.
Shortly after implementing this, we started receiving integrity errors on th
e database on a daily basis.
Many of the errors are requiring checktable with repair data loss to correct
the problem. The corruption has shown up on both replicated and non-replic
ated tables, but only occurs if replication is running. As soon as replicat
ion was stopped, the databa
se quit reporting integrity errors.
Please let me know if you need further information.
Has anyone else ran into this?I don't think replication has anything to do with it. Probably replication
is stressing your hard disk subsystem, leading to errors. So the real
culprit could be hardware. Check your event viewer and any hardware logs for
clues.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ghost" <anonymous@.discussions.microsoft.com> wrote in message
news:B6B0118A-C15D-41A5-9E11-FA01F4AD14BD@.microsoft.com...
We are running SQL 2000 EI SP3 on a Windows 2000 Adv. Server.
We have recently setup a database for replication using transactional
replication every ten minutes.
Shortly after implementing this, we started receiving integrity errors on
the database on a daily basis.
Many of the errors are requiring checktable with repair data loss to correct
the problem. The corruption has shown up on both replicated and
non-replicated tables, but only occurs if replication is running. As soon
as replication was stopped, the database quit reporting integrity errors.
Please let me know if you need further information.
Has anyone else ran into this?|||Our first thought was hardware as well, however, a few things are pointing t
o something else causing the problem:
1. All of the hardware is brand new, and the server is running at about a q
uarter of our target performance. (This server is not yet hosting databases
that will be added later this year... During peak time we are seeing a max u
tilization of 15% across
all processors). The hardware vendor has already been over this server and
hasn't found anything, and there is no hardware related errors in the server
event logs
2. This is the first enterprise class server we have run in a SAN environme
nt. To eliminate the SAN hardware or network we moved all of the data to in
ternal drives on the server. The problem continues to occur.
3. This server is hosting multiple application databases. The only databas
e with errors is the replicated database. If this was hardware related we w
ould expect to see the other databases having problems, as they were using t
he same internal hardware
and SAN array to hold their data as the replicated database.
Any thoughts?|||Okay, could you post the exact errors you are seeing in the SQL Server error
logs?
Are you replicating text or image columns?
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ghost" <anonymous@.discussions.microsoft.com> wrote in message
news:34BB1D32-6935-40A8-B061-1372260A868B@.microsoft.com...
Our first thought was hardware as well, however, a few things are pointing
to something else causing the problem:
1. All of the hardware is brand new, and the server is running at about a
quarter of our target performance. (This server is not yet hosting databases
that will be added later this year... During peak time we are seeing a max
utilization of 15% across all processors). The hardware vendor has already
been over this server and hasn't found anything, and there is no hardware
related errors in the server event logs
2. This is the first enterprise class server we have run in a SAN
environment. To eliminate the SAN hardware or network we moved all of the
data to internal drives on the server. The problem continues to occur.
3. This server is hosting multiple application databases. The only
database with errors is the replicated database. If this was hardware
related we would expect to see the other databases having problems, as they
were using the same internal hardware and SAN array to hold their data as
the replicated database.
Any thoughts?|||Yes, There are both image and text columns in some of the tables.
Below is excerpt from the maintenance log on the errors we are getting:
[1] Database ServiceCenter: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8929: [Microsoft][ODBC SQL Server Driv
er][SQL Server]Object ID 525244926: Errors found in text ID 462078345216 own
ed by data record identified by RID = (1:202550:3).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 525244926. The te
xt, ntext, or image node at page (1:40468), slot 12, text ID 462078345216 is
referenced by page (1:202550), slot 3, but was not seen in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 525244926. The te
xt, ntext, or image node at page (1:695828), slot 12, text ID 462078345216 i
s not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Database 'ServiceCenter', i
ndex 'applicationm1.applicationm1_P' (ID 1589580701) (index ID 2). Extra or
invalid key for the keys:
[Microsoft][ODBC SQL Server Driver][SQL Server]Index row (1:81744:140) with values (app
lication = 'cc.find.problem' and label = 'build.s) points to the data row id
entified by (RID = (1:348126:8)).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 3
consistency errors in table 'problemm1' (object ID 525244926).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 1
consistency errors in table 'applicationm1' (object ID 1589580701).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation errors and 4
consistency errors in database 'ServiceCenter'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the minimum re
pair level for the errors found by DBCC CHECKDB (ServiceCenter ).|||There are a lot of bugs/problems, replicating text/image columns. First make
sure all participating servers are on the latest service pack. Then see if
you find any hits for those error numbers at: http://support.microsoft.com
And consider contacting Microsoft support.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"Ghost" <anonymous@.discussions.microsoft.com> wrote in message
news:07926FA4-64B3-4038-8934-E2A3A631DDE3@.microsoft.com...
Yes, There are both image and text columns in some of the tables.
Below is excerpt from the maintenance log on the errors we are getting:
[1] Database ServiceCenter: Check Data and Index Linkage...
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8929: [Microsoft][ODBC SQL
Server Driver][SQL Server]Object ID 525244926: Errors found in text ID
462078345216 owned by data record identified by RID = (1:202550:3).
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
525244926. The text, ntext, or image node at page (1:40468), slot 12, text
ID 462078345216 is referenced by page (1:202550), slot 3, but was not seen
in the scan.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID
525244926. The text, ntext, or image node at page (1:695828), slot 12, text
ID 462078345216 is not referenced.
[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Database
'ServiceCenter', index 'applicationm1.applicationm1_P' (ID 1589580701)
(index ID 2). Extra or invalid key for the keys:
[Microsoft][ODBC SQL Server Driver][SQL Server]Index row (1:81744:140) with
values (application = 'cc.find.problem' and label = 'build.s) points to the
data row identified by (RID = (1:348126:8)).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 3 consistency errors in table 'problemm1' (object ID 525244926).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 1 consistency errors in table 'applicationm1' (object ID
1589580701).
[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 0 allocation
errors and 4 consistency errors in database 'ServiceCenter'.
[Microsoft][ODBC SQL Server Driver][SQL Server]repair_allow_data_loss is the
minimum repair level for the errors found by DBCC CHECKDB (ServiceCenter ).

Data corruption in ldf when debugging WinForm app

I'm trying to build my 1st WinForm app which uses SqlExpress and when I click Debug and test my app everything is fine (though occasionally I do get time out errors - but that's another question I guess), however I can't then debug the app again because I get the following error:

"The log scan number (34:410:82) passed to log scan in database '3D1D0C232D2C55B0EF6C455470CD3D4C_S\\VISUAL STUDIO 2005\\PROJECTS\\MYFIRSTAPP\\MYFIRSTAPP\\BIN\\DEBUG\\OTJDB.MDF' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf). If this error occurred during replication, re-create the publication. Otherwise, restore from backup if the problem results in a failure during startup. \r\nAn error occurred during recovery, preventing the database '3D1D0C232D2C55B0EF6C455470CD3D4C_S\\VISUAL STUDIO 2005\\PROJECTS\\MYFIRSTAPP\\MYFIRSTAPP\\BIN\\DEBUG\\OTJDB.MDF' (database ID 5) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.\r\nCannot open user default database. Login failed.\r\nLogin failed for user 'SQurreL\\Simon'."

I can't delete the ldf or mdb files in the debug\bin folder because they are in use, so I have to stop the SQLExpress service, kill the sqlserv.exe process, delete the ldf and mdb files, then restart the SQLExpress service and try again... which is beginning to get right on my nerves now

Can anyone help with my sanity please?

Hi ganseki,

I think the error message has claimed very clearly: " .....that the log file (.ldf) does not match the data file (.mdf)." If mdf file and the corresponding ldf file cannot match, we cannot open that database again--that's designed by microsoft. So, we need to "If this error occurred during replication, re-create the publication. Otherwise, restore from backup..".

I have to stop the SQLExpress service, kill the sqlserv.exe process, delete the ldf and mdb files, then restart the SQLExpress service and try again

I think what you did is right. So, does this error still occure after you did that? Also i'm curious about what you did to that database thru your application, that you get that error message.

Hope my suggestion helps

|||

Thanks for the reply.

Any idea why that is happening each time I debug the app? Or is it normal for WinForms development to have to jump through those hoops in order to test the changes.

It takes longer to stop the service, kill the process, delete the files and restart the service than to make a change to a column width in a datagridview, which if I then find is too narrow or too wide means I have to go through that whole process again just to check that changing the width from 150 to 100 isn't enough? This involves no change to the database, all that would have happened is a select to get the data for the grid, but it happens even without any database interaction - i.e. just opening the app (which starts with a blank page).

After debugging I click the close button on the form, the app closes and Visual Studio quits debug mode. I make changes (which can be as trivial as my illustration above) and then have to go through that routine. And that happens each and every time I want to debug.

It is driving meinsane
Is there something I should be doing differently to stop this from happening?

data corruption -- dbcc checkdb repair doesn't work

SQL Server 2000 SP 3 (8.00.818), Windows 2003 Server, 2 processors, 1 GB of
RAM
We have a 400 MB database that started having 7102 and 7105 Fatal errors
today when using simple select statments and drop table commands. An example
error message is below:
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 7102 occurred at Nov 29 2004 11:41AM
The event log does not provide a lot more detail:
DESCRIPTION: Error: 7102, Severity: 20, State: 7
SQL Server Internal Error. Text manager cannot continue with current
statement.
We tried using DBCC Checkdb, and found quite a few issues. We then ran the
following in single user mode:
DBCC Checkdb (Mydatabase_20041129, REPAIR_ALLOW_DATA_LOSS)
This resulted in the massive output below and suggests that some errors
could not be fixed. I noticed several references to "text, ntext, or
image". There is only 1 of those datatypes in any of the databases columns,
and that is an image datatype in the dtproperties table, which we certainly
have not messed with. What is the next logical way of attempting to resolve
this issue?
Thanks in advance! We really appreciate it.
Mark
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4464050176 owned by data record
identified by RID = (1:80:6) id = 304056169 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 2982150144 owned by data record
identified by RID = (1:1527:1) id = 2130822653 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4385865728 owned by data record
identified by RID = (1:24044:0) id = 224055884 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386127872 owned by data record
identified by RID = (1:24044:4) id = 224055884 and indid = 9.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386193408 owned by data record
identified by RID = (1:24044:5) id = 224055884 and indid = 10.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386324480 owned by data record
identified by RID = (1:24044:12) id = 240055941 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386390016 owned by data record
identified by RID = (1:24044:13) id = 240055941 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386455552 owned by data record
identified by RID = (1:24044:14) id = 240055941 and indid = 8.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4385800192 owned by data record
identified by RID = (1:25939:5) id = 224055884 and indid = 4.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:6722),
slot 0, text ID 2982150144 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:10321),
slot 0, text ID 4464050176 does not match its reference from page (1:14833),
slot 3.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or
image node page (1:10321), slot 0, text ID 4464050176 is pointed to by page
(1:10321), slot 2 and by page (1:14833), slot 3.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14055),
slot 8, text ID 4386324480 is referenced by page (1:24044), slot 12, but was
not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14055),
slot 10, text ID 4386390016 is referenced by page (1:24044), slot 13, but
was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14055),
slot 11, text ID 4386455552 is referenced by page (1:24044), slot 14, but
was not seen in the scan.
DBCC results for 'Mydatabase_20041129'.
DBCC results for 'sysobjects'.
There are 677 rows in 14 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
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.
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.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:27801),
slot 0, text ID 4386193408 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:27805),
slot 0, text ID 4386455552 is not referenced.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:33615),
slot 2, text ID 4385800192 is referenced by page (1:25939), slot 5, but was
not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:33615),
slot 4, text ID 4385865728 is referenced by page (1:24044), slot 0, but was
not seen in the scan.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:50317),
slot 0, text ID 4366532608 does not match its reference from page (1:12277),
slot 3.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:50317),
slot 1, text ID 4386193408 is referenced by page (1:24044), slot 5, but was
not seen in the scan.
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.
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.
There are 1029 rows in 102 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 21 consistency errors in table
'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 2826 rows in 99 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 583 rows in 171 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 383 rows in 2 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 24 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 6 rows in 1 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 4596 rows in 26 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 59 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 't_sv_look_cce_stdnt_status'.
There are 5 rows in 1 pages for object 't_sv_look_cce_stdnt_status'.
DBCC results for 't_sv_rpt_stdnt_icp_contact'.
There are 3843 rows in 1179 pages for object 't_sv_rpt_stdnt_icp_contact'.
DBCC results for 't_sv_look_sex'.
There are 3 rows in 1 pages for object 't_sv_look_sex'.
DBCC results for 't_sv_rpt_stdnt_pil_contact'.
There are 867 rows in 100 pages for object 't_sv_rpt_stdnt_pil_contact'.
DBCC results for 't_sv_app_interaction'.
There are 5321 rows in 334 pages for object 't_sv_app_interaction'.
DBCC results for 't_sv_app_stdnt_mktg_category'.
There are 9 rows in 1 pages for object 't_sv_app_stdnt_mktg_category'.
DBCC results for 't_sv_rpt_stdnt_u_ndg_contact'.
There are 124060 rows in 3807 pages for object
't_sv_rpt_stdnt_u_ndg_contact'.
DBCC results for 't_sv_look_dw_degree_level'.
There are 488 rows in 5 pages for object 't_sv_look_dw_degree_level'.
DBCC results for 't_sv_rpt_stdnt_g_ndg_contact'.
There are 3171 rows in 325 pages for object 't_sv_rpt_stdnt_g_ndg_contact'.
DBCC results for 't_sv_app_stdnt'.
There are 134815 rows in 2402 pages for object 't_sv_app_stdnt'.
DBCC results for 't_sv_look_how_contacted_type'.
There are 5 rows in 1 pages for object 't_sv_look_how_contacted_type'.
DBCC results for 't_sv_rpt_stdnt_all_dcp_complete'.
There are 12376 rows in 902 pages for object
't_sv_rpt_stdnt_all_dcp_complete'.
DBCC results for 't_sv_rpt_stdnt_all_contact'.
There are 133387 rows in 2744 pages for object 't_sv_rpt_stdnt_all_contact'.
DBCC results for 't_sv_app_stdnt_story_lead'.
There are 28 rows in 3 pages for object 't_sv_app_stdnt_story_lead'.
DBCC results for 't_sv_look_how_heard_type'.
There are 11 rows in 1 pages for object 't_sv_look_how_heard_type'.
DBCC results for 't_sv_temp_all_stdnts_by_sub_plan_m'.
There are 10768 rows in 143 pages for object
't_sv_temp_all_stdnts_by_sub_plan_m'.
DBCC results for 't_sv_temp_stdnt_plan_milestone_m'.
There are 155186 rows in 1743 pages for object
't_sv_temp_stdnt_plan_milestone_m'.
DBCC results for 't_sv_temp_app_stdnt_u'.
There are 23941 rows in 209 pages for object 't_sv_temp_app_stdnt_u'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_key_words'.
There are 9 rows in 5 pages for object
't_sv_rpt_mktg_stdnt_story_key_words'.
DBCC results for 't_sv_look_dw_honors_type'.
There are 7 rows in 1 pages for object 't_sv_look_dw_honors_type'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 't_sv_temp_stdnt_demographics_m'.
There are 130101 rows in 3428 pages for object
't_sv_temp_stdnt_demographics_m'.
DBCC results for 't_sv_temp_all_stdnts_by_plan_m'.
There are 135219 rows in 3238 pages for object
't_sv_temp_all_stdnts_by_plan_m'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_notes'.
There are 0 rows in 2 pages for object 't_sv_rpt_mktg_stdnt_story_notes'.
DBCC results for 't_sv_temp_staff_demographics_m'.
There are 171 rows in 7 pages for object 't_sv_temp_staff_demographics_m'.
DBCC results for 't_sv_app_staff'.
There are 296 rows in 7 pages for object 't_sv_app_staff'.
DBCC results for 't_sv_rpt_stdnt_bas_complete'.
There are 2768 rows in 158 pages for object 't_sv_rpt_stdnt_bas_complete'.
DBCC results for 't_sv_app_stdnt_mktg_note'.
There are 0 rows in 1 pages for object 't_sv_app_stdnt_mktg_note'.
DBCC results for 't_sv_rpt_stdnt_crt_complete'.
There are 1758 rows in 110 pages for object 't_sv_rpt_stdnt_crt_complete'.
DBCC results for 't_sv_look_dw_stdnt_group'.
There are 597 rows in 5 pages for object 't_sv_look_dw_stdnt_group'.
DBCC results for 't_sv_look_bas_application_type'.
There are 2 rows in 1 pages for object 't_sv_look_bas_application_type'.
DBCC results for 't_sv_app_stdnt_stdnt_group'.
There are 91753 rows in 239 pages for object 't_sv_app_stdnt_stdnt_group'.
DBCC results for 't_sv_look_cce_appt_type'.
There are 9 rows in 1 pages for object 't_sv_look_cce_appt_type'.
DBCC results for 't_sv_rpt_stdnt_acad_subplan_all'.
There are 8459 rows in 24 pages for object
't_sv_rpt_stdnt_acad_subplan_all'.
DBCC results for 't_sv_look_interpreting_language'.
There are 8 rows in 1 pages for object 't_sv_look_interpreting_language'.
DBCC results for 't_sv_rpt_stdnt_icp_complete'.
There are 3843 rows in 323 pages for object 't_sv_rpt_stdnt_icp_complete'.
DBCC results for 't_sv_admin_last_id_used'.
There are 0 rows in 0 pages for object 't_sv_admin_last_id_used'.
DBCC results for 't_sv_conversion_institution'.
There are 10856 rows in 80 pages for object 't_sv_conversion_institution'.
DBCC results for 't_sv_look_interpreting_crt_status'.
There are 11 rows in 1 pages for object 't_sv_look_interpreting_crt_status'.
DBCC results for 't_sv_rpt_stdnt_pil_complete'.
There are 853 rows in 49 pages for object 't_sv_rpt_stdnt_pil_complete'.
DBCC results for 't_sv_rpt_advising'.
There are 1702 rows in 195 pages for object 't_sv_rpt_advising'.
DBCC results for 't_sv_look_dw_degree_checkout_status'.
There are 7 rows in 1 pages for object
't_sv_look_dw_degree_checkout_status'.
DBCC results for 't_sv_look_dw_term'.
There are 521 rows in 15 pages for object 't_sv_look_dw_term'.
DBCC results for 't_sv_look_dw_institution'.
There are 49024 rows in 293 pages for object 't_sv_look_dw_institution'.
DBCC results for 't_LastIdUsed'.
There are 1 rows in 3 pages for object 't_LastIdUsed'.
DBCC results for 't_sv_rpt_stdnt_interpreting_crt_complete'.
There are 409 rows in 64 pages for object
't_sv_rpt_stdnt_interpreting_crt_complete'.
DBCC results for 't_sv_app_person_education_umn'.
There are 0 rows in 1 pages for object 't_sv_app_person_education_umn'.
DBCC results for 'ICP_ALUMNI'.
There are 2466 rows in 217 pages for object 'ICP_ALUMNI'.
DBCC results for 'studenR3'.
There are 1201 rows in 91 pages for object 'studenR3'.
DBCC results for 't_sv_app_staff_cce_plan_type'.
There are 310 rows in 1 pages for object 't_sv_app_staff_cce_plan_type'.
DBCC results for 'tblstudentinfo'.
There are 129 rows in 5 pages for object 'tblstudentinfo'.
DBCC results for 't_sv_app_stdnt_acad_progress'.
There are 1924 rows in 7 pages for object 't_sv_app_stdnt_acad_progress'.
DBCC results for 'Graduate_Students'.
There are 133 rows in 6 pages for object 'Graduate_Students'.
DBCC results for 'PreadmitStudents'.
There are 682 rows in 77 pages for object 'PreadmitStudents'.
DBCC results for 't_sv_admin_navigation_person_info_menu'.
There are 18 rows in 1 pages for object
't_sv_admin_navigation_person_info_menu'.
DBCC results for 't_sv_look_group'.
There are 2 rows in 1 pages for object 't_sv_look_group'.
DBCC results for 't_sv_rpt_person_all_contact'.
There are 134279 rows in 2676 pages for object
't_sv_rpt_person_all_contact'.
DBCC results for 't_sv_look_institution'.
There are 278 rows in 2 pages for object 't_sv_look_institution'.
DBCC results for 't_sv_rpt_staff_all_contact'.
There are 259 rows in 12 pages for object 't_sv_rpt_staff_all_contact'.
DBCC results for 't_sv_admin_navigation_acad_plan_info_menu'.
There are 4 rows in 1 pages for object
't_sv_admin_navigation_acad_plan_info_menu'.
DBCC results for 't_sv_look_degree_level'.
There are 11 rows in 1 pages for object 't_sv_look_degree_level'.
DBCC results for 't_sv_app_stdnt_plan'.
There are 140747 rows in 3006 pages for object 't_sv_app_stdnt_plan'.
DBCC results for 't_sv_app_stdnt_staff'.
There are 1713 rows in 19 pages for object 't_sv_app_stdnt_staff'.
DBCC results for 't_sv_rpt_staff_by_program_contact'.
There are 246 rows in 25 pages for object
't_sv_rpt_staff_by_program_contact'.
DBCC results for 'studenR3_old'.
There are 1372 rows in 116 pages for object 'studenR3_old'.
DBCC results for 't_sv_rpt_stdnt_international_complete'.
There are 472 rows in 25 pages for object
't_sv_rpt_stdnt_international_complete'.
DBCC results for 't_sv_app_person_education'.
There are 1685 rows in 10 pages for object 't_sv_app_person_education'.
DBCC results for 't_sv_app_stdnt_mls'.
There are 3215 rows in 18 pages for object 't_sv_app_stdnt_mls'.
DBCC results for 't_sv_look_dw_staff_level'.
There are 108 rows in 1 pages for object 't_sv_look_dw_staff_level'.
DBCC results for 't_sv_rpt_mls_mailing'.
There are 471 rows in 8 pages for object 't_sv_rpt_mls_mailing'.
DBCC results for 't_sv_look_addr_type'.
There are 4 rows in 1 pages for object 't_sv_look_addr_type'.
DBCC results for 't_sv_rpt_stdnt_mls_contact'.
There are 3140 rows in 98 pages for object 't_sv_rpt_stdnt_mls_contact'.
DBCC results for 't_sv_look_milestone'.
There are 22 rows in 1 pages for object 't_sv_look_milestone'.
DBCC results for 'PreadmitStudents_old'.
There are 664 rows in 72 pages for object 'PreadmitStudents_old'.
DBCC results for 't_sv_look_dw_prog_status'.
There are 12 rows in 4 pages for object 't_sv_look_dw_prog_status'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_contact_info'.
There are 14 rows in 5 pages for object
't_sv_rpt_mktg_stdnt_story_contact_info'.
DBCC results for 't_sv_app_stdnt_plan_milestone'.
There are 157105 rows in 912 pages for object
't_sv_app_stdnt_plan_milestone'.
DBCC results for 't_sv_look_dw_ethnic_group'.
There are 7 rows in 4 pages for object 't_sv_look_dw_ethnic_group'.
DBCC results for 't_sv_rpt_stdnt_mls_complete'.
There are 3140 rows in 209 pages for object 't_sv_rpt_stdnt_mls_complete'.
DBCC results for 't_sv_look_dw_dir_exclude'.
There are 7 rows in 4 pages for object 't_sv_look_dw_dir_exclude'.
DBCC results for 't_sv_look_dw_acad_prog'.
There are 53 rows in 7 pages for object 't_sv_look_dw_acad_prog'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_lead_info'.
There are 28 rows in 7 pages for object
't_sv_rpt_mktg_stdnt_story_lead_info'.
DBCC results for 't_sv_look_dw_acad_plan'.
There are 99 rows in 11 pages for object 't_sv_look_dw_acad_plan'.
DBCC results for 'ICP_ALUMNI_old'.
There are 2358 rows in 205 pages for object 'ICP_ALUMNI_old'.
DBCC results for 't_sv_app_person'.
There are 135045 rows in 2089 pages for object 't_sv_app_person'.
DBCC results for 't_sv_app_stdnt_icp'.
There are 3864 rows in 16 pages for object 't_sv_app_stdnt_icp'.
DBCC results for 'icp_term_conversion'.
There are 120 rows in 1 pages for object 'icp_term_conversion'.
DBCC results for 't_sv_look_interaction_type'.
There are 6 rows in 1 pages for object 't_sv_look_interaction_type'.
DBCC results for 'studenR3_062404'.
There are 1391 rows in 124 pages for object 'studenR3_062404'.
DBCC results for 't_sv_rpt_stdnt_notes'.
There are 5251 rows in 428 pages for object 't_sv_rpt_stdnt_notes'.
DBCC results for 't_sv_rpt_stdnt_crt_contact'.
There are 1758 rows in 84 pages for object 't_sv_rpt_stdnt_crt_contact'.
DBCC results for 'ICP_ALUMNI_06242004'.
There are 2346 rows in 213 pages for object 'ICP_ALUMNI_06242004'.
DBCC results for 't_sv_app_stdnt_pil'.
There are 868 rows in 6 pages for object 't_sv_app_stdnt_pil'.
DBCC results for 't_sv_look_interaction_location_type'.
There are 4 rows in 1 pages for object
't_sv_look_interaction_location_type'.
DBCC results for 't_sv_app_stdnt_crt'.
There are 1798 rows in 10 pages for object 't_sv_app_stdnt_crt'.
DBCC results for 't_sv_look_mktg_category'.
There are 10 rows in 1 pages for object 't_sv_look_mktg_category'.
DBCC results for 't_sv_look_phone_type'.
There are 7 rows in 1 pages for object 't_sv_look_phone_type'.
DBCC results for 'PIL_area_specialists'.
There are 119 rows in 1 pages for object 'PIL_area_specialists'.
DBCC results for 't_sv_look_stdnt_story_lead'.
There are 5 rows in 1 pages for object 't_sv_look_stdnt_story_lead'.
DBCC results for 't_sv_look_cce_stdnt_status_sub'.
There are 18 rows in 1 pages for object 't_sv_look_cce_stdnt_status_sub'.
DBCC results for 't_sv_look_mktg_contact_type'.
There are 2 rows in 1 pages for object 't_sv_look_mktg_contact_type'.
DBCC results for 't_sv_admin_archive_plan_term_status'.
There are 0 rows in 0 pages for object
't_sv_admin_archive_plan_term_status'.
DBCC results for 't_sv_app_person_addr'.
There are 190774 rows in 1748 pages for object 't_sv_app_person_addr'.
DBCC results for 't_sv_look_email_type'.
There are 5 rows in 1 pages for object 't_sv_look_email_type'.
DBCC results for 't_sv_look_dw_subplan'.
There are 409 rows in 3 pages for object 't_sv_look_dw_subplan'.
DBCC results for 't_sv_app_person_email'.
There are 81864 rows in 547 pages for object 't_sv_app_person_email'.
DBCC results for 't_sv_app_person_phone'.
There are 106574 rows in 612 pages for object 't_sv_app_person_phone'.
DBCC results for 't_sv_app_stdnt_bas'.
There are 2797 rows in 7 pages for object 't_sv_app_stdnt_bas'.
DBCC results for 't_sv_look_dw_acad_progress_type'.
There are 8 rows in 1 pages for object 't_sv_look_dw_acad_progress_type'.
DBCC results for 'PreadmitStudents_07142004'.
There are 684 rows in 154 pages for object 'PreadmitStudents_07142004'.
DBCC results for 't_sv_app_stdnt_interpreting_crt'.
There are 292 rows in 4 pages for object 't_sv_app_stdnt_interpreting_crt'.
DBCC results for 'tblstudentinfo_07142004'.
There are 140 rows in 6 pages for object 'tblstudentinfo_07142004'.
DBCC results for 't_sv_look_employer'.
There are 798 rows in 4 pages for object 't_sv_look_employer'.
DBCC results for 't_sv_app_person_group'.
There are 38 rows in 1 pages for object 't_sv_app_person_group'.
DBCC results for 'preadmit_pil_staff_logins'.
There are 7 rows in 1 pages for object 'preadmit_pil_staff_logins'.
DBCC results for 't_sv_look_occupation_category'.
There are 31 rows in 1 pages for object 't_sv_look_occupation_category'.
DBCC results for 'Graduate_Students_07152004'.
There are 130 rows in 6 pages for object 'Graduate_Students_07152004'.
DBCC results for 't_sv_admin_history'.
There are 4640 rows in 46 pages for object 't_sv_admin_history'.
DBCC results for 't_sv_rpt_stdnt_bas_contact'.
There are 2768 rows in 222 pages for object 't_sv_rpt_stdnt_bas_contact'.
DBCC results for 't_sv_app_stdnt_plan_subplan'.
There are 10037 rows in 48 pages for object 't_sv_app_stdnt_plan_subplan'.
DBCC results for 't_sv_look_cce_plan_type'.
There are 8 rows in 1 pages for object 't_sv_look_cce_plan_type'.
DBCC results for 'icp_advisor_lookup'.
There are 6 rows in 1 pages for object 'icp_advisor_lookup'.
CHECKDB found 0 allocation errors and 21 consistency errors in database
'Mydatabase_20041129'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.
If the db is that badly damaged your best bet is to call MS PSS and see what
they can do. In any case your best option with damage sucha s that is to
restore from the last good backup.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Mark" <Mark@.nowhere.com> wrote in message
news:%23k31Qok1EHA.1260@.TK2MSFTNGP12.phx.gbl...
> SQL Server 2000 SP 3 (8.00.818), Windows 2003 Server, 2 processors, 1 GB
> of
> RAM
> We have a 400 MB database that started having 7102 and 7105 Fatal errors
> today when using simple select statments and drop table commands. An
> example
> error message is below:
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 7102 occurred at Nov 29 2004 11:41AM
> The event log does not provide a lot more detail:
> DESCRIPTION: Error: 7102, Severity: 20, State: 7
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
> We tried using DBCC Checkdb, and found quite a few issues. We then ran
> the
> following in single user mode:
> DBCC Checkdb (Mydatabase_20041129, REPAIR_ALLOW_DATA_LOSS)
> This resulted in the massive output below and suggests that some errors
> could not be fixed. I noticed several references to "text, ntext, or
> image". There is only 1 of those datatypes in any of the databases
> columns,
> and that is an image datatype in the dtproperties table, which we
> certainly
> have not messed with. What is the next logical way of attempting to
> resolve
> this issue?
> Thanks in advance! We really appreciate it.
> Mark
>
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4464050176 owned by data record
> identified by RID = (1:80:6) id = 304056169 and indid = 5.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 2982150144 owned by data record
> identified by RID = (1:1527:1) id = 2130822653 and indid = 2.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4385865728 owned by data record
> identified by RID = (1:24044:0) id = 224055884 and indid = 5.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386127872 owned by data record
> identified by RID = (1:24044:4) id = 224055884 and indid = 9.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386193408 owned by data record
> identified by RID = (1:24044:5) id = 224055884 and indid = 10.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386324480 owned by data record
> identified by RID = (1:24044:12) id = 240055941 and indid = 6.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386390016 owned by data record
> identified by RID = (1:24044:13) id = 240055941 and indid = 7.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386455552 owned by data record
> identified by RID = (1:24044:14) id = 240055941 and indid = 8.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4385800192 owned by data record
> identified by RID = (1:25939:5) id = 224055884 and indid = 4.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page (1:6722),
> slot 0, text ID 2982150144 is not referenced.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:10321),
> slot 0, text ID 4464050176 does not match its reference from page
> (1:14833),
> slot 3.
> Server: Msg 8974, Level 16, State 1, Line 1
> Text node referenced by more than one node. Object ID 2, text, ntext, or
> image node page (1:10321), slot 0, text ID 4464050176 is pointed to by
> page
> (1:10321), slot 2 and by page (1:14833), slot 3.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:14055),
> slot 8, text ID 4386324480 is referenced by page (1:24044), slot 12, but
> was
> not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:14055),
> slot 10, text ID 4386390016 is referenced by page (1:24044), slot 13, but
> was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:14055),
> slot 11, text ID 4386455552 is referenced by page (1:24044), slot 14, but
> was not seen in the scan.
> DBCC results for 'Mydatabase_20041129'.
> DBCC results for 'sysobjects'.
> There are 677 rows in 14 pages for object 'sysobjects'.
> DBCC results for 'sysindexes'.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> 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.
> 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.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:27801),
> slot 0, text ID 4386193408 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:27805),
> slot 0, text ID 4386455552 is not referenced.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:33615),
> slot 2, text ID 4385800192 is referenced by page (1:25939), slot 5, but
> was
> not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:33615),
> slot 4, text ID 4385865728 is referenced by page (1:24044), slot 0, but
> was
> not seen in the scan.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:50317),
> slot 0, text ID 4366532608 does not match its reference from page
> (1:12277),
> slot 3.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:50317),
> slot 1, text ID 4386193408 is referenced by page (1:24044), slot 5, but
> was
> not seen in the scan.
> 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.
> 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.
> There are 1029 rows in 102 pages for object 'sysindexes'.
> CHECKDB found 0 allocation errors and 21 consistency errors in table
> 'sysindexes' (object ID 2).
> DBCC results for 'syscolumns'.
> There are 2826 rows in 99 pages for object 'syscolumns'.
> DBCC results for 'systypes'.
> There are 26 rows in 1 pages for object 'systypes'.
> DBCC results for 'syscomments'.
> There are 583 rows in 171 pages for object 'syscomments'.
> DBCC results for 'sysfiles1'.
> There are 2 rows in 1 pages for object 'sysfiles1'.
> DBCC results for 'syspermissions'.
> There are 383 rows in 2 pages for object 'syspermissions'.
> DBCC results for 'sysusers'.
> There are 24 rows in 1 pages for object 'sysusers'.
> DBCC results for 'sysproperties'.
> There are 6 rows in 1 pages for object 'sysproperties'.
> DBCC results for 'sysdepends'.
> There are 4596 rows in 26 pages for object 'sysdepends'.
> DBCC results for 'sysreferences'.
> There are 59 rows in 1 pages for object 'sysreferences'.
> DBCC results for 'sysfulltextcatalogs'.
> There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
> DBCC results for 'sysfulltextnotify'.
> There are 0 rows in 0 pages for object 'sysfulltextnotify'.
> DBCC results for 'sysfilegroups'.
> There are 1 rows in 1 pages for object 'sysfilegroups'.
> DBCC results for 't_sv_look_cce_stdnt_status'.
> There are 5 rows in 1 pages for object 't_sv_look_cce_stdnt_status'.
> DBCC results for 't_sv_rpt_stdnt_icp_contact'.
> There are 3843 rows in 1179 pages for object 't_sv_rpt_stdnt_icp_contact'.
> DBCC results for 't_sv_look_sex'.
> There are 3 rows in 1 pages for object 't_sv_look_sex'.
> DBCC results for 't_sv_rpt_stdnt_pil_contact'.
> There are 867 rows in 100 pages for object 't_sv_rpt_stdnt_pil_contact'.
> DBCC results for 't_sv_app_interaction'.
> There are 5321 rows in 334 pages for object 't_sv_app_interaction'.
> DBCC results for 't_sv_app_stdnt_mktg_category'.
> There are 9 rows in 1 pages for object 't_sv_app_stdnt_mktg_category'.
> DBCC results for 't_sv_rpt_stdnt_u_ndg_contact'.
> There are 124060 rows in 3807 pages for object
> 't_sv_rpt_stdnt_u_ndg_contact'.
> DBCC results for 't_sv_look_dw_degree_level'.
> There are 488 rows in 5 pages for object 't_sv_look_dw_degree_level'.
> DBCC results for 't_sv_rpt_stdnt_g_ndg_contact'.
> There are 3171 rows in 325 pages for object
> 't_sv_rpt_stdnt_g_ndg_contact'.
> DBCC results for 't_sv_app_stdnt'.
> There are 134815 rows in 2402 pages for object 't_sv_app_stdnt'.
> DBCC results for 't_sv_look_how_contacted_type'.
> There are 5 rows in 1 pages for object 't_sv_look_how_contacted_type'.
> DBCC results for 't_sv_rpt_stdnt_all_dcp_complete'.
> There are 12376 rows in 902 pages for object
> 't_sv_rpt_stdnt_all_dcp_complete'.
> DBCC results for 't_sv_rpt_stdnt_all_contact'.
> There are 133387 rows in 2744 pages for object
> 't_sv_rpt_stdnt_all_contact'.
> DBCC results for 't_sv_app_stdnt_story_lead'.
> There are 28 rows in 3 pages for object 't_sv_app_stdnt_story_lead'.
> DBCC results for 't_sv_look_how_heard_type'.
> There are 11 rows in 1 pages for object 't_sv_look_how_heard_type'.
> DBCC results for 't_sv_temp_all_stdnts_by_sub_plan_m'.
> There are 10768 rows in 143 pages for object
> 't_sv_temp_all_stdnts_by_sub_plan_m'.
> DBCC results for 't_sv_temp_stdnt_plan_milestone_m'.
> There are 155186 rows in 1743 pages for object
> 't_sv_temp_stdnt_plan_milestone_m'.
> DBCC results for 't_sv_temp_app_stdnt_u'.
> There are 23941 rows in 209 pages for object 't_sv_temp_app_stdnt_u'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_key_words'.
> There are 9 rows in 5 pages for object
> 't_sv_rpt_mktg_stdnt_story_key_words'.
> DBCC results for 't_sv_look_dw_honors_type'.
> There are 7 rows in 1 pages for object 't_sv_look_dw_honors_type'.
> DBCC results for 'dtproperties'.
> There are 0 rows in 0 pages for object 'dtproperties'.
> DBCC results for 't_sv_temp_stdnt_demographics_m'.
> There are 130101 rows in 3428 pages for object
> 't_sv_temp_stdnt_demographics_m'.
> DBCC results for 't_sv_temp_all_stdnts_by_plan_m'.
> There are 135219 rows in 3238 pages for object
> 't_sv_temp_all_stdnts_by_plan_m'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_notes'.
> There are 0 rows in 2 pages for object 't_sv_rpt_mktg_stdnt_story_notes'.
> DBCC results for 't_sv_temp_staff_demographics_m'.
> There are 171 rows in 7 pages for object 't_sv_temp_staff_demographics_m'.
> DBCC results for 't_sv_app_staff'.
> There are 296 rows in 7 pages for object 't_sv_app_staff'.
> DBCC results for 't_sv_rpt_stdnt_bas_complete'.
> There are 2768 rows in 158 pages for object 't_sv_rpt_stdnt_bas_complete'.
> DBCC results for 't_sv_app_stdnt_mktg_note'.
> There are 0 rows in 1 pages for object 't_sv_app_stdnt_mktg_note'.
> DBCC results for 't_sv_rpt_stdnt_crt_complete'.
> There are 1758 rows in 110 pages for object 't_sv_rpt_stdnt_crt_complete'.
> DBCC results for 't_sv_look_dw_stdnt_group'.
> There are 597 rows in 5 pages for object 't_sv_look_dw_stdnt_group'.
> DBCC results for 't_sv_look_bas_application_type'.
> There are 2 rows in 1 pages for object 't_sv_look_bas_application_type'.
> DBCC results for 't_sv_app_stdnt_stdnt_group'.
> There are 91753 rows in 239 pages for object 't_sv_app_stdnt_stdnt_group'.
> DBCC results for 't_sv_look_cce_appt_type'.
> There are 9 rows in 1 pages for object 't_sv_look_cce_appt_type'.
> DBCC results for 't_sv_rpt_stdnt_acad_subplan_all'.
> There are 8459 rows in 24 pages for object
> 't_sv_rpt_stdnt_acad_subplan_all'.
> DBCC results for 't_sv_look_interpreting_language'.
> There are 8 rows in 1 pages for object 't_sv_look_interpreting_language'.
> DBCC results for 't_sv_rpt_stdnt_icp_complete'.
> There are 3843 rows in 323 pages for object 't_sv_rpt_stdnt_icp_complete'.
> DBCC results for 't_sv_admin_last_id_used'.
> There are 0 rows in 0 pages for object 't_sv_admin_last_id_used'.
> DBCC results for 't_sv_conversion_institution'.
> There are 10856 rows in 80 pages for object 't_sv_conversion_institution'.
> DBCC results for 't_sv_look_interpreting_crt_status'.
> There are 11 rows in 1 pages for object
> 't_sv_look_interpreting_crt_status'.
> DBCC results for 't_sv_rpt_stdnt_pil_complete'.
> There are 853 rows in 49 pages for object 't_sv_rpt_stdnt_pil_complete'.
> DBCC results for 't_sv_rpt_advising'.
> There are 1702 rows in 195 pages for object 't_sv_rpt_advising'.
> DBCC results for 't_sv_look_dw_degree_checkout_status'.
> There are 7 rows in 1 pages for object
> 't_sv_look_dw_degree_checkout_status'.
> DBCC results for 't_sv_look_dw_term'.
> There are 521 rows in 15 pages for object 't_sv_look_dw_term'.
> DBCC results for 't_sv_look_dw_institution'.
> There are 49024 rows in 293 pages for object 't_sv_look_dw_institution'.
> DBCC results for 't_LastIdUsed'.
> There are 1 rows in 3 pages for object 't_LastIdUsed'.
> DBCC results for 't_sv_rpt_stdnt_interpreting_crt_complete'.
> There are 409 rows in 64 pages for object
> 't_sv_rpt_stdnt_interpreting_crt_complete'.
> DBCC results for 't_sv_app_person_education_umn'.
> There are 0 rows in 1 pages for object 't_sv_app_person_education_umn'.
> DBCC results for 'ICP_ALUMNI'.
> There are 2466 rows in 217 pages for object 'ICP_ALUMNI'.
> DBCC results for 'studenR3'.
> There are 1201 rows in 91 pages for object 'studenR3'.
> DBCC results for 't_sv_app_staff_cce_plan_type'.
> There are 310 rows in 1 pages for object 't_sv_app_staff_cce_plan_type'.
> DBCC results for 'tblstudentinfo'.
> There are 129 rows in 5 pages for object 'tblstudentinfo'.
> DBCC results for 't_sv_app_stdnt_acad_progress'.
> There are 1924 rows in 7 pages for object 't_sv_app_stdnt_acad_progress'.
> DBCC results for 'Graduate_Students'.
> There are 133 rows in 6 pages for object 'Graduate_Students'.
> DBCC results for 'PreadmitStudents'.
> There are 682 rows in 77 pages for object 'PreadmitStudents'.
> DBCC results for 't_sv_admin_navigation_person_info_menu'.
> There are 18 rows in 1 pages for object
> 't_sv_admin_navigation_person_info_menu'.
> DBCC results for 't_sv_look_group'.
> There are 2 rows in 1 pages for object 't_sv_look_group'.
> DBCC results for 't_sv_rpt_person_all_contact'.
> There are 134279 rows in 2676 pages for object
> 't_sv_rpt_person_all_contact'.
> DBCC results for 't_sv_look_institution'.
> There are 278 rows in 2 pages for object 't_sv_look_institution'.
> DBCC results for 't_sv_rpt_staff_all_contact'.
> There are 259 rows in 12 pages for object 't_sv_rpt_staff_all_contact'.
> DBCC results for 't_sv_admin_navigation_acad_plan_info_menu'.
> There are 4 rows in 1 pages for object
> 't_sv_admin_navigation_acad_plan_info_menu'.
> DBCC results for 't_sv_look_degree_level'.
> There are 11 rows in 1 pages for object 't_sv_look_degree_level'.
> DBCC results for 't_sv_app_stdnt_plan'.
> There are 140747 rows in 3006 pages for object 't_sv_app_stdnt_plan'.
> DBCC results for 't_sv_app_stdnt_staff'.
> There are 1713 rows in 19 pages for object 't_sv_app_stdnt_staff'.
> DBCC results for 't_sv_rpt_staff_by_program_contact'.
> There are 246 rows in 25 pages for object
> 't_sv_rpt_staff_by_program_contact'.
> DBCC results for 'studenR3_old'.
> There are 1372 rows in 116 pages for object 'studenR3_old'.
> DBCC results for 't_sv_rpt_stdnt_international_complete'.
> There are 472 rows in 25 pages for object
> 't_sv_rpt_stdnt_international_complete'.
> DBCC results for 't_sv_app_person_education'.
> There are 1685 rows in 10 pages for object 't_sv_app_person_education'.
> DBCC results for 't_sv_app_stdnt_mls'.
> There are 3215 rows in 18 pages for object 't_sv_app_stdnt_mls'.
> DBCC results for 't_sv_look_dw_staff_level'.
> There are 108 rows in 1 pages for object 't_sv_look_dw_staff_level'.
> DBCC results for 't_sv_rpt_mls_mailing'.
> There are 471 rows in 8 pages for object 't_sv_rpt_mls_mailing'.
> DBCC results for 't_sv_look_addr_type'.
> There are 4 rows in 1 pages for object 't_sv_look_addr_type'.
> DBCC results for 't_sv_rpt_stdnt_mls_contact'.
> There are 3140 rows in 98 pages for object 't_sv_rpt_stdnt_mls_contact'.
> DBCC results for 't_sv_look_milestone'.
> There are 22 rows in 1 pages for object 't_sv_look_milestone'.
> DBCC results for 'PreadmitStudents_old'.
> There are 664 rows in 72 pages for object 'PreadmitStudents_old'.
> DBCC results for 't_sv_look_dw_prog_status'.
> There are 12 rows in 4 pages for object 't_sv_look_dw_prog_status'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_contact_info'.
> There are 14 rows in 5 pages for object
> 't_sv_rpt_mktg_stdnt_story_contact_info'.
> DBCC results for 't_sv_app_stdnt_plan_milestone'.
> There are 157105 rows in 912 pages for object
> 't_sv_app_stdnt_plan_milestone'.
> DBCC results for 't_sv_look_dw_ethnic_group'.
> There are 7 rows in 4 pages for object 't_sv_look_dw_ethnic_group'.
> DBCC results for 't_sv_rpt_stdnt_mls_complete'.
> There are 3140 rows in 209 pages for object 't_sv_rpt_stdnt_mls_complete'.
> DBCC results for 't_sv_look_dw_dir_exclude'.
> There are 7 rows in 4 pages for object 't_sv_look_dw_dir_exclude'.
> DBCC results for 't_sv_look_dw_acad_prog'.
> There are 53 rows in 7 pages for object 't_sv_look_dw_acad_prog'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_lead_info'.
> There are 28 rows in 7 pages for object
> 't_sv_rpt_mktg_stdnt_story_lead_info'.
> DBCC results for 't_sv_look_dw_acad_plan'.
> There are 99 rows in 11 pages for object 't_sv_look_dw_acad_plan'.
> DBCC results for 'ICP_ALUMNI_old'.
> There are 2358 rows in 205 pages for object 'ICP_ALUMNI_old'.
> DBCC results for 't_sv_app_person'.
> There are 135045 rows in 2089 pages for object 't_sv_app_person'.
> DBCC results for 't_sv_app_stdnt_icp'.
> There are 3864 rows in 16 pages for object 't_sv_app_stdnt_icp'.
> DBCC results for 'icp_term_conversion'.
> There are 120 rows in 1 pages for object 'icp_term_conversion'.
> DBCC results for 't_sv_look_interaction_type'.
> There are 6 rows in 1 pages for object 't_sv_look_interaction_type'.
> DBCC results for 'studenR3_062404'.
> There are 1391 rows in 124 pages for object 'studenR3_062404'.
> DBCC results for 't_sv_rpt_stdnt_notes'.
> There are 5251 rows in 428 pages for object 't_sv_rpt_stdnt_notes'.
> DBCC results for 't_sv_rpt_stdnt_crt_contact'.
> There are 1758 rows in 84 pages for object 't_sv_rpt_stdnt_crt_contact'.
> DBCC results for 'ICP_ALUMNI_06242004'.
> There are 2346 rows in 213 pages for object 'ICP_ALUMNI_06242004'.
> DBCC results for 't_sv_app_stdnt_pil'.
> There are 868 rows in 6 pages for object 't_sv_app_stdnt_pil'.
> DBCC results for 't_sv_look_interaction_location_type'.
> There are 4 rows in 1 pages for object
> 't_sv_look_interaction_location_type'.
> DBCC results for 't_sv_app_stdnt_crt'.
> There are 1798 rows in 10 pages for object 't_sv_app_stdnt_crt'.
> DBCC results for 't_sv_look_mktg_category'.
> There are 10 rows in 1 pages for object 't_sv_look_mktg_category'.
> DBCC results for 't_sv_look_phone_type'.
> There are 7 rows in 1 pages for object 't_sv_look_phone_type'.
> DBCC results for 'PIL_area_specialists'.
> There are 119 rows in 1 pages for object 'PIL_area_specialists'.
> DBCC results for 't_sv_look_stdnt_story_lead'.
> There are 5 rows in 1 pages for object 't_sv_look_stdnt_story_lead'.
> DBCC results for 't_sv_look_cce_stdnt_status_sub'.
> There are 18 rows in 1 pages for object 't_sv_look_cce_stdnt_status_sub'.
> DBCC results for 't_sv_look_mktg_contact_type'.
> There are 2 rows in 1 pages for object 't_sv_look_mktg_contact_type'.
> DBCC results for 't_sv_admin_archive_plan_term_status'.
> There are 0 rows in 0 pages for object
> 't_sv_admin_archive_plan_term_status'.
> DBCC results for 't_sv_app_person_addr'.
> There are 190774 rows in 1748 pages for object 't_sv_app_person_addr'.
> DBCC results for 't_sv_look_email_type'.
> There are 5 rows in 1 pages for object 't_sv_look_email_type'.
> DBCC results for 't_sv_look_dw_subplan'.
> There are 409 rows in 3 pages for object 't_sv_look_dw_subplan'.
> DBCC results for 't_sv_app_person_email'.
> There are 81864 rows in 547 pages for object 't_sv_app_person_email'.
> DBCC results for 't_sv_app_person_phone'.
> There are 106574 rows in 612 pages for object 't_sv_app_person_phone'.
> DBCC results for 't_sv_app_stdnt_bas'.
> There are 2797 rows in 7 pages for object 't_sv_app_stdnt_bas'.
> DBCC results for 't_sv_look_dw_acad_progress_type'.
> There are 8 rows in 1 pages for object 't_sv_look_dw_acad_progress_type'.
> DBCC results for 'PreadmitStudents_07142004'.
> There are 684 rows in 154 pages for object 'PreadmitStudents_07142004'.
> DBCC results for 't_sv_app_stdnt_interpreting_crt'.
> There are 292 rows in 4 pages for object
> 't_sv_app_stdnt_interpreting_crt'.
> DBCC results for 'tblstudentinfo_07142004'.
> There are 140 rows in 6 pages for object 'tblstudentinfo_07142004'.
> DBCC results for 't_sv_look_employer'.
> There are 798 rows in 4 pages for object 't_sv_look_employer'.
> DBCC results for 't_sv_app_person_group'.
> There are 38 rows in 1 pages for object 't_sv_app_person_group'.
> DBCC results for 'preadmit_pil_staff_logins'.
> There are 7 rows in 1 pages for object 'preadmit_pil_staff_logins'.
> DBCC results for 't_sv_look_occupation_category'.
> There are 31 rows in 1 pages for object 't_sv_look_occupation_category'.
> DBCC results for 'Graduate_Students_07152004'.
> There are 130 rows in 6 pages for object 'Graduate_Students_07152004'.
> DBCC results for 't_sv_admin_history'.
> There are 4640 rows in 46 pages for object 't_sv_admin_history'.
> DBCC results for 't_sv_rpt_stdnt_bas_contact'.
> There are 2768 rows in 222 pages for object 't_sv_rpt_stdnt_bas_contact'.
> DBCC results for 't_sv_app_stdnt_plan_subplan'.
> There are 10037 rows in 48 pages for object 't_sv_app_stdnt_plan_subplan'.
> DBCC results for 't_sv_look_cce_plan_type'.
> There are 8 rows in 1 pages for object 't_sv_look_cce_plan_type'.
> DBCC results for 'icp_advisor_lookup'.
> There are 6 rows in 1 pages for object 'icp_advisor_lookup'.
> CHECKDB found 0 allocation errors and 21 consistency errors in database
> 'Mydatabase_20041129'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>
|||As Andrew says, restore is your best option for all corruptions. You should
also analyze your system to see what caused the problems.
In fact, in this case, restore is your only option as the corruptions are in
sysindexes and cannot be repaired.
You should contact PSS to help you.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eS#4oFl1EHA.1652@.TK2MSFTNGP11.phx.gbl...
> If the db is that badly damaged your best bet is to call MS PSS and see
what[vbcol=seagreen]
> they can do. In any case your best option with damage sucha s that is to
> restore from the last good backup.
>
> http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
> http://www.mssqlserver.com/faq/general-pss.asp MS PSS
> --
> Andrew J. Kelly SQL MVP
>
> "Mark" <Mark@.nowhere.com> wrote in message
> news:%23k31Qok1EHA.1260@.TK2MSFTNGP12.phx.gbl...
(1:6722),[vbcol=seagreen]
but[vbcol=seagreen]
but[vbcol=seagreen]
't_sv_rpt_stdnt_icp_contact'.[vbcol=seagreen]
't_sv_rpt_mktg_stdnt_story_notes'.[vbcol=seagreen]
't_sv_temp_staff_demographics_m'.[vbcol=seagreen]
't_sv_rpt_stdnt_bas_complete'.[vbcol=seagreen]
't_sv_rpt_stdnt_crt_complete'.[vbcol=seagreen]
't_sv_app_stdnt_stdnt_group'.[vbcol=seagreen]
't_sv_look_interpreting_language'.[vbcol=seagreen]
't_sv_rpt_stdnt_icp_complete'.[vbcol=seagreen]
't_sv_conversion_institution'.[vbcol=seagreen]
't_sv_app_stdnt_acad_progress'.[vbcol=seagreen]
't_sv_rpt_stdnt_mls_complete'.[vbcol=seagreen]
't_sv_look_cce_stdnt_status_sub'.[vbcol=seagreen]
't_sv_look_dw_acad_progress_type'.[vbcol=seagreen]
't_sv_rpt_stdnt_bas_contact'.[vbcol=seagreen]
't_sv_app_stdnt_plan_subplan'.
>

data corruption -- dbcc checkdb repair doesn't work

SQL Server 2000 SP 3 (8.00.818), Windows 2003 Server, 2 processors, 1 GB of
RAM
We have a 400 MB database that started having 7102 and 7105 Fatal errors
today when using simple select statments and drop table commands. An example
error message is below:
Server: Msg 21, Level 20, State 1, Line 1
Warning: Fatal error 7102 occurred at Nov 29 2004 11:41AM
The event log does not provide a lot more detail:
DESCRIPTION: Error: 7102, Severity: 20, State: 7
SQL Server Internal Error. Text manager cannot continue with current
statement.
We tried using DBCC Checkdb, and found quite a few issues. We then ran the
following in single user mode:
DBCC Checkdb (Mydatabase_20041129, REPAIR_ALLOW_DATA_LOSS)
This resulted in the massive output below and suggests that some errors
could not be fixed. I noticed several references to "text, ntext, or
image". There is only 1 of those datatypes in any of the databases columns,
and that is an image datatype in the dtproperties table, which we certainly
have not messed with. What is the next logical way of attempting to resolve
this issue?
Thanks in advance! We really appreciate it.
Mark
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4464050176 owned by data record
identified by RID = (1:80:6) id = 304056169 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 2982150144 owned by data record
identified by RID = (1:1527:1) id = 2130822653 and indid = 2.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4385865728 owned by data record
identified by RID = (1:24044:0) id = 224055884 and indid = 5.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386127872 owned by data record
identified by RID = (1:24044:4) id = 224055884 and indid = 9.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386193408 owned by data record
identified by RID = (1:24044:5) id = 224055884 and indid = 10.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386324480 owned by data record
identified by RID = (1:24044:12) id = 240055941 and indid = 6.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386390016 owned by data record
identified by RID = (1:24044:13) id = 240055941 and indid = 7.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4386455552 owned by data record
identified by RID = (1:24044:14) id = 240055941 and indid = 8.
Server: Msg 8929, Level 16, State 1, Line 1
Object ID 2: Errors found in text ID 4385800192 owned by data record
identified by RID = (1:25939:5) id = 224055884 and indid = 4.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:6722),
slot 0, text ID 2982150144 is not referenced.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:10321),
slot 0, text ID 4464050176 does not match its reference from page (1:14833),
slot 3.
Server: Msg 8974, Level 16, State 1, Line 1
Text node referenced by more than one node. Object ID 2, text, ntext, or
image node page (1:10321), slot 0, text ID 4464050176 is pointed to by page
(1:10321), slot 2 and by page (1:14833), slot 3.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14055),
slot 8, text ID 4386324480 is referenced by page (1:24044), slot 12, but was
not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14055),
slot 10, text ID 4386390016 is referenced by page (1:24044), slot 13, but
was not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:14055),
slot 11, text ID 4386455552 is referenced by page (1:24044), slot 14, but
was not seen in the scan.
DBCC results for 'Mydatabase_20041129'.
DBCC results for 'sysobjects'.
There are 677 rows in 14 pages for object 'sysobjects'.
DBCC results for 'sysindexes'.
The repair level on the DBCC statement caused this repair to be
bypassed.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
The system cannot self repair this error.
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.
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.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:27801),
slot 0, text ID 4386193408 is not referenced.
Server: Msg 8964, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:27805),
slot 0, text ID 4386455552 is not referenced.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:33615),
slot 2, text ID 4385800192 is referenced by page (1:25939), slot 5, but was
not seen in the scan.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:33615),
slot 4, text ID 4385865728 is referenced by page (1:24044), slot 0, but was
not seen in the scan.
Server: Msg 8961, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:50317),
slot 0, text ID 4366532608 does not match its reference from page (1:12277),
slot 3.
Server: Msg 8965, Level 16, State 1, Line 1
Table error: Object ID 2. The text, ntext, or image node at page (1:50317),
slot 1, text ID 4386193408 is referenced by page (1:24044), slot 5, but was
not seen in the scan.
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.
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.
There are 1029 rows in 102 pages for object 'sysindexes'.
CHECKDB found 0 allocation errors and 21 consistency errors in table
'sysindexes' (object ID 2).
DBCC results for 'syscolumns'.
There are 2826 rows in 99 pages for object 'syscolumns'.
DBCC results for 'systypes'.
There are 26 rows in 1 pages for object 'systypes'.
DBCC results for 'syscomments'.
There are 583 rows in 171 pages for object 'syscomments'.
DBCC results for 'sysfiles1'.
There are 2 rows in 1 pages for object 'sysfiles1'.
DBCC results for 'syspermissions'.
There are 383 rows in 2 pages for object 'syspermissions'.
DBCC results for 'sysusers'.
There are 24 rows in 1 pages for object 'sysusers'.
DBCC results for 'sysproperties'.
There are 6 rows in 1 pages for object 'sysproperties'.
DBCC results for 'sysdepends'.
There are 4596 rows in 26 pages for object 'sysdepends'.
DBCC results for 'sysreferences'.
There are 59 rows in 1 pages for object 'sysreferences'.
DBCC results for 'sysfulltextcatalogs'.
There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
DBCC results for 'sysfulltextnotify'.
There are 0 rows in 0 pages for object 'sysfulltextnotify'.
DBCC results for 'sysfilegroups'.
There are 1 rows in 1 pages for object 'sysfilegroups'.
DBCC results for 't_sv_look_cce_stdnt_status'.
There are 5 rows in 1 pages for object 't_sv_look_cce_stdnt_status'.
DBCC results for 't_sv_rpt_stdnt_icp_contact'.
There are 3843 rows in 1179 pages for object 't_sv_rpt_stdnt_icp_contact'.
DBCC results for 't_sv_look_sex'.
There are 3 rows in 1 pages for object 't_sv_look_sex'.
DBCC results for 't_sv_rpt_stdnt_pil_contact'.
There are 867 rows in 100 pages for object 't_sv_rpt_stdnt_pil_contact'.
DBCC results for 't_sv_app_interaction'.
There are 5321 rows in 334 pages for object 't_sv_app_interaction'.
DBCC results for 't_sv_app_stdnt_mktg_category'.
There are 9 rows in 1 pages for object 't_sv_app_stdnt_mktg_category'.
DBCC results for 't_sv_rpt_stdnt_u_ndg_contact'.
There are 124060 rows in 3807 pages for object
't_sv_rpt_stdnt_u_ndg_contact'.
DBCC results for 't_sv_look_dw_degree_level'.
There are 488 rows in 5 pages for object 't_sv_look_dw_degree_level'.
DBCC results for 't_sv_rpt_stdnt_g_ndg_contact'.
There are 3171 rows in 325 pages for object 't_sv_rpt_stdnt_g_ndg_contact'.
DBCC results for 't_sv_app_stdnt'.
There are 134815 rows in 2402 pages for object 't_sv_app_stdnt'.
DBCC results for 't_sv_look_how_contacted_type'.
There are 5 rows in 1 pages for object 't_sv_look_how_contacted_type'.
DBCC results for 't_sv_rpt_stdnt_all_dcp_complete'.
There are 12376 rows in 902 pages for object
't_sv_rpt_stdnt_all_dcp_complete'.
DBCC results for 't_sv_rpt_stdnt_all_contact'.
There are 133387 rows in 2744 pages for object 't_sv_rpt_stdnt_all_contact'.
DBCC results for 't_sv_app_stdnt_story_lead'.
There are 28 rows in 3 pages for object 't_sv_app_stdnt_story_lead'.
DBCC results for 't_sv_look_how_heard_type'.
There are 11 rows in 1 pages for object 't_sv_look_how_heard_type'.
DBCC results for 't_sv_temp_all_stdnts_by_sub_plan_m'.
There are 10768 rows in 143 pages for object
't_sv_temp_all_stdnts_by_sub_plan_m'.
DBCC results for 't_sv_temp_stdnt_plan_milestone_m'.
There are 155186 rows in 1743 pages for object
't_sv_temp_stdnt_plan_milestone_m'.
DBCC results for 't_sv_temp_app_stdnt_u'.
There are 23941 rows in 209 pages for object 't_sv_temp_app_stdnt_u'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_key_words'.
There are 9 rows in 5 pages for object
't_sv_rpt_mktg_stdnt_story_key_words'.
DBCC results for 't_sv_look_dw_honors_type'.
There are 7 rows in 1 pages for object 't_sv_look_dw_honors_type'.
DBCC results for 'dtproperties'.
There are 0 rows in 0 pages for object 'dtproperties'.
DBCC results for 't_sv_temp_stdnt_demographics_m'.
There are 130101 rows in 3428 pages for object
't_sv_temp_stdnt_demographics_m'.
DBCC results for 't_sv_temp_all_stdnts_by_plan_m'.
There are 135219 rows in 3238 pages for object
't_sv_temp_all_stdnts_by_plan_m'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_notes'.
There are 0 rows in 2 pages for object 't_sv_rpt_mktg_stdnt_story_notes'.
DBCC results for 't_sv_temp_staff_demographics_m'.
There are 171 rows in 7 pages for object 't_sv_temp_staff_demographics_m'.
DBCC results for 't_sv_app_staff'.
There are 296 rows in 7 pages for object 't_sv_app_staff'.
DBCC results for 't_sv_rpt_stdnt_bas_complete'.
There are 2768 rows in 158 pages for object 't_sv_rpt_stdnt_bas_complete'.
DBCC results for 't_sv_app_stdnt_mktg_note'.
There are 0 rows in 1 pages for object 't_sv_app_stdnt_mktg_note'.
DBCC results for 't_sv_rpt_stdnt_crt_complete'.
There are 1758 rows in 110 pages for object 't_sv_rpt_stdnt_crt_complete'.
DBCC results for 't_sv_look_dw_stdnt_group'.
There are 597 rows in 5 pages for object 't_sv_look_dw_stdnt_group'.
DBCC results for 't_sv_look_bas_application_type'.
There are 2 rows in 1 pages for object 't_sv_look_bas_application_type'.
DBCC results for 't_sv_app_stdnt_stdnt_group'.
There are 91753 rows in 239 pages for object 't_sv_app_stdnt_stdnt_group'.
DBCC results for 't_sv_look_cce_appt_type'.
There are 9 rows in 1 pages for object 't_sv_look_cce_appt_type'.
DBCC results for 't_sv_rpt_stdnt_acad_subplan_all'.
There are 8459 rows in 24 pages for object
't_sv_rpt_stdnt_acad_subplan_all'.
DBCC results for 't_sv_look_interpreting_language'.
There are 8 rows in 1 pages for object 't_sv_look_interpreting_language'.
DBCC results for 't_sv_rpt_stdnt_icp_complete'.
There are 3843 rows in 323 pages for object 't_sv_rpt_stdnt_icp_complete'.
DBCC results for 't_sv_admin_last_id_used'.
There are 0 rows in 0 pages for object 't_sv_admin_last_id_used'.
DBCC results for 't_sv_conversion_institution'.
There are 10856 rows in 80 pages for object 't_sv_conversion_institution'.
DBCC results for 't_sv_look_interpreting_crt_status'.
There are 11 rows in 1 pages for object 't_sv_look_interpreting_crt_status'.
DBCC results for 't_sv_rpt_stdnt_pil_complete'.
There are 853 rows in 49 pages for object 't_sv_rpt_stdnt_pil_complete'.
DBCC results for 't_sv_rpt_advising'.
There are 1702 rows in 195 pages for object 't_sv_rpt_advising'.
DBCC results for 't_sv_look_dw_degree_checkout_status'.
There are 7 rows in 1 pages for object
't_sv_look_dw_degree_checkout_status'.
DBCC results for 't_sv_look_dw_term'.
There are 521 rows in 15 pages for object 't_sv_look_dw_term'.
DBCC results for 't_sv_look_dw_institution'.
There are 49024 rows in 293 pages for object 't_sv_look_dw_institution'.
DBCC results for 't_LastIdUsed'.
There are 1 rows in 3 pages for object 't_LastIdUsed'.
DBCC results for 't_sv_rpt_stdnt_interpreting_crt_complete'.
There are 409 rows in 64 pages for object
't_sv_rpt_stdnt_interpreting_crt_complete'.
DBCC results for 't_sv_app_person_education_umn'.
There are 0 rows in 1 pages for object 't_sv_app_person_education_umn'.
DBCC results for 'ICP_ALUMNI'.
There are 2466 rows in 217 pages for object 'ICP_ALUMNI'.
DBCC results for 'studenR3'.
There are 1201 rows in 91 pages for object 'studenR3'.
DBCC results for 't_sv_app_staff_cce_plan_type'.
There are 310 rows in 1 pages for object 't_sv_app_staff_cce_plan_type'.
DBCC results for 'tblstudentinfo'.
There are 129 rows in 5 pages for object 'tblstudentinfo'.
DBCC results for 't_sv_app_stdnt_acad_progress'.
There are 1924 rows in 7 pages for object 't_sv_app_stdnt_acad_progress'.
DBCC results for 'Graduate_Students'.
There are 133 rows in 6 pages for object 'Graduate_Students'.
DBCC results for 'PreadmitStudents'.
There are 682 rows in 77 pages for object 'PreadmitStudents'.
DBCC results for 't_sv_admin_navigation_person_info_menu'.
There are 18 rows in 1 pages for object
't_sv_admin_navigation_person_info_menu'.
DBCC results for 't_sv_look_group'.
There are 2 rows in 1 pages for object 't_sv_look_group'.
DBCC results for 't_sv_rpt_person_all_contact'.
There are 134279 rows in 2676 pages for object
't_sv_rpt_person_all_contact'.
DBCC results for 't_sv_look_institution'.
There are 278 rows in 2 pages for object 't_sv_look_institution'.
DBCC results for 't_sv_rpt_staff_all_contact'.
There are 259 rows in 12 pages for object 't_sv_rpt_staff_all_contact'.
DBCC results for 't_sv_admin_navigation_acad_plan_info_menu'.
There are 4 rows in 1 pages for object
't_sv_admin_navigation_acad_plan_info_menu'.
DBCC results for 't_sv_look_degree_level'.
There are 11 rows in 1 pages for object 't_sv_look_degree_level'.
DBCC results for 't_sv_app_stdnt_plan'.
There are 140747 rows in 3006 pages for object 't_sv_app_stdnt_plan'.
DBCC results for 't_sv_app_stdnt_staff'.
There are 1713 rows in 19 pages for object 't_sv_app_stdnt_staff'.
DBCC results for 't_sv_rpt_staff_by_program_contact'.
There are 246 rows in 25 pages for object
't_sv_rpt_staff_by_program_contact'.
DBCC results for 'studenR3_old'.
There are 1372 rows in 116 pages for object 'studenR3_old'.
DBCC results for 't_sv_rpt_stdnt_international_complete'.
There are 472 rows in 25 pages for object
't_sv_rpt_stdnt_international_complete'.
DBCC results for 't_sv_app_person_education'.
There are 1685 rows in 10 pages for object 't_sv_app_person_education'.
DBCC results for 't_sv_app_stdnt_mls'.
There are 3215 rows in 18 pages for object 't_sv_app_stdnt_mls'.
DBCC results for 't_sv_look_dw_staff_level'.
There are 108 rows in 1 pages for object 't_sv_look_dw_staff_level'.
DBCC results for 't_sv_rpt_mls_mailing'.
There are 471 rows in 8 pages for object 't_sv_rpt_mls_mailing'.
DBCC results for 't_sv_look_addr_type'.
There are 4 rows in 1 pages for object 't_sv_look_addr_type'.
DBCC results for 't_sv_rpt_stdnt_mls_contact'.
There are 3140 rows in 98 pages for object 't_sv_rpt_stdnt_mls_contact'.
DBCC results for 't_sv_look_milestone'.
There are 22 rows in 1 pages for object 't_sv_look_milestone'.
DBCC results for 'PreadmitStudents_old'.
There are 664 rows in 72 pages for object 'PreadmitStudents_old'.
DBCC results for 't_sv_look_dw_prog_status'.
There are 12 rows in 4 pages for object 't_sv_look_dw_prog_status'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_contact_info'.
There are 14 rows in 5 pages for object
't_sv_rpt_mktg_stdnt_story_contact_info'.
DBCC results for 't_sv_app_stdnt_plan_milestone'.
There are 157105 rows in 912 pages for object
't_sv_app_stdnt_plan_milestone'.
DBCC results for 't_sv_look_dw_ethnic_group'.
There are 7 rows in 4 pages for object 't_sv_look_dw_ethnic_group'.
DBCC results for 't_sv_rpt_stdnt_mls_complete'.
There are 3140 rows in 209 pages for object 't_sv_rpt_stdnt_mls_complete'.
DBCC results for 't_sv_look_dw_dir_exclude'.
There are 7 rows in 4 pages for object 't_sv_look_dw_dir_exclude'.
DBCC results for 't_sv_look_dw_acad_prog'.
There are 53 rows in 7 pages for object 't_sv_look_dw_acad_prog'.
DBCC results for 't_sv_rpt_mktg_stdnt_story_lead_info'.
There are 28 rows in 7 pages for object
't_sv_rpt_mktg_stdnt_story_lead_info'.
DBCC results for 't_sv_look_dw_acad_plan'.
There are 99 rows in 11 pages for object 't_sv_look_dw_acad_plan'.
DBCC results for 'ICP_ALUMNI_old'.
There are 2358 rows in 205 pages for object 'ICP_ALUMNI_old'.
DBCC results for 't_sv_app_person'.
There are 135045 rows in 2089 pages for object 't_sv_app_person'.
DBCC results for 't_sv_app_stdnt_icp'.
There are 3864 rows in 16 pages for object 't_sv_app_stdnt_icp'.
DBCC results for 'icp_term_conversion'.
There are 120 rows in 1 pages for object 'icp_term_conversion'.
DBCC results for 't_sv_look_interaction_type'.
There are 6 rows in 1 pages for object 't_sv_look_interaction_type'.
DBCC results for 'studenR3_062404'.
There are 1391 rows in 124 pages for object 'studenR3_062404'.
DBCC results for 't_sv_rpt_stdnt_notes'.
There are 5251 rows in 428 pages for object 't_sv_rpt_stdnt_notes'.
DBCC results for 't_sv_rpt_stdnt_crt_contact'.
There are 1758 rows in 84 pages for object 't_sv_rpt_stdnt_crt_contact'.
DBCC results for 'ICP_ALUMNI_06242004'.
There are 2346 rows in 213 pages for object 'ICP_ALUMNI_06242004'.
DBCC results for 't_sv_app_stdnt_pil'.
There are 868 rows in 6 pages for object 't_sv_app_stdnt_pil'.
DBCC results for 't_sv_look_interaction_location_type'.
There are 4 rows in 1 pages for object
't_sv_look_interaction_location_type'.
DBCC results for 't_sv_app_stdnt_crt'.
There are 1798 rows in 10 pages for object 't_sv_app_stdnt_crt'.
DBCC results for 't_sv_look_mktg_category'.
There are 10 rows in 1 pages for object 't_sv_look_mktg_category'.
DBCC results for 't_sv_look_phone_type'.
There are 7 rows in 1 pages for object 't_sv_look_phone_type'.
DBCC results for 'PIL_area_specialists'.
There are 119 rows in 1 pages for object 'PIL_area_specialists'.
DBCC results for 't_sv_look_stdnt_story_lead'.
There are 5 rows in 1 pages for object 't_sv_look_stdnt_story_lead'.
DBCC results for 't_sv_look_cce_stdnt_status_sub'.
There are 18 rows in 1 pages for object 't_sv_look_cce_stdnt_status_sub'.
DBCC results for 't_sv_look_mktg_contact_type'.
There are 2 rows in 1 pages for object 't_sv_look_mktg_contact_type'.
DBCC results for 't_sv_admin_archive_plan_term_status'.
There are 0 rows in 0 pages for object
't_sv_admin_archive_plan_term_status'.
DBCC results for 't_sv_app_person_addr'.
There are 190774 rows in 1748 pages for object 't_sv_app_person_addr'.
DBCC results for 't_sv_look_email_type'.
There are 5 rows in 1 pages for object 't_sv_look_email_type'.
DBCC results for 't_sv_look_dw_subplan'.
There are 409 rows in 3 pages for object 't_sv_look_dw_subplan'.
DBCC results for 't_sv_app_person_email'.
There are 81864 rows in 547 pages for object 't_sv_app_person_email'.
DBCC results for 't_sv_app_person_phone'.
There are 106574 rows in 612 pages for object 't_sv_app_person_phone'.
DBCC results for 't_sv_app_stdnt_bas'.
There are 2797 rows in 7 pages for object 't_sv_app_stdnt_bas'.
DBCC results for 't_sv_look_dw_acad_progress_type'.
There are 8 rows in 1 pages for object 't_sv_look_dw_acad_progress_type'.
DBCC results for 'PreadmitStudents_07142004'.
There are 684 rows in 154 pages for object 'PreadmitStudents_07142004'.
DBCC results for 't_sv_app_stdnt_interpreting_crt'.
There are 292 rows in 4 pages for object 't_sv_app_stdnt_interpreting_crt'.
DBCC results for 'tblstudentinfo_07142004'.
There are 140 rows in 6 pages for object 'tblstudentinfo_07142004'.
DBCC results for 't_sv_look_employer'.
There are 798 rows in 4 pages for object 't_sv_look_employer'.
DBCC results for 't_sv_app_person_group'.
There are 38 rows in 1 pages for object 't_sv_app_person_group'.
DBCC results for 'preadmit_pil_staff_logins'.
There are 7 rows in 1 pages for object 'preadmit_pil_staff_logins'.
DBCC results for 't_sv_look_occupation_category'.
There are 31 rows in 1 pages for object 't_sv_look_occupation_category'.
DBCC results for 'Graduate_Students_07152004'.
There are 130 rows in 6 pages for object 'Graduate_Students_07152004'.
DBCC results for 't_sv_admin_history'.
There are 4640 rows in 46 pages for object 't_sv_admin_history'.
DBCC results for 't_sv_rpt_stdnt_bas_contact'.
There are 2768 rows in 222 pages for object 't_sv_rpt_stdnt_bas_contact'.
DBCC results for 't_sv_app_stdnt_plan_subplan'.
There are 10037 rows in 48 pages for object 't_sv_app_stdnt_plan_subplan'.
DBCC results for 't_sv_look_cce_plan_type'.
There are 8 rows in 1 pages for object 't_sv_look_cce_plan_type'.
DBCC results for 'icp_advisor_lookup'.
There are 6 rows in 1 pages for object 'icp_advisor_lookup'.
CHECKDB found 0 allocation errors and 21 consistency errors in database
'Mydatabase_20041129'.
DBCC execution completed. If DBCC printed error messages, contact your
system administrator.If the db is that badly damaged your best bet is to call MS PSS and see what
they can do. In any case your best option with damage sucha s that is to
restore from the last good backup.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"Mark" <Mark@.nowhere.com> wrote in message
news:%23k31Qok1EHA.1260@.TK2MSFTNGP12.phx.gbl...
> SQL Server 2000 SP 3 (8.00.818), Windows 2003 Server, 2 processors, 1 GB
> of
> RAM
> We have a 400 MB database that started having 7102 and 7105 Fatal errors
> today when using simple select statments and drop table commands. An
> example
> error message is below:
> Server: Msg 21, Level 20, State 1, Line 1
> Warning: Fatal error 7102 occurred at Nov 29 2004 11:41AM
> The event log does not provide a lot more detail:
> DESCRIPTION: Error: 7102, Severity: 20, State: 7
> SQL Server Internal Error. Text manager cannot continue with current
> statement.
> We tried using DBCC Checkdb, and found quite a few issues. We then ran
> the
> following in single user mode:
> DBCC Checkdb (Mydatabase_20041129, REPAIR_ALLOW_DATA_LOSS)
> This resulted in the massive output below and suggests that some errors
> could not be fixed. I noticed several references to "text, ntext, or
> image". There is only 1 of those datatypes in any of the databases
> columns,
> and that is an image datatype in the dtproperties table, which we
> certainly
> have not messed with. What is the next logical way of attempting to
> resolve
> this issue?
> Thanks in advance! We really appreciate it.
> Mark
>
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4464050176 owned by data record
> identified by RID = (1:80:6) id = 304056169 and indid = 5.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 2982150144 owned by data record
> identified by RID = (1:1527:1) id = 2130822653 and indid = 2.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4385865728 owned by data record
> identified by RID = (1:24044:0) id = 224055884 and indid = 5.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386127872 owned by data record
> identified by RID = (1:24044:4) id = 224055884 and indid = 9.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386193408 owned by data record
> identified by RID = (1:24044:5) id = 224055884 and indid = 10.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386324480 owned by data record
> identified by RID = (1:24044:12) id = 240055941 and indid = 6.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386390016 owned by data record
> identified by RID = (1:24044:13) id = 240055941 and indid = 7.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4386455552 owned by data record
> identified by RID = (1:24044:14) id = 240055941 and indid = 8.
> Server: Msg 8929, Level 16, State 1, Line 1
> Object ID 2: Errors found in text ID 4385800192 owned by data record
> identified by RID = (1:25939:5) id = 224055884 and indid = 4.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page (1:6722),
> slot 0, text ID 2982150144 is not referenced.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:10321),
> slot 0, text ID 4464050176 does not match its reference from page
> (1:14833),
> slot 3.
> Server: Msg 8974, Level 16, State 1, Line 1
> Text node referenced by more than one node. Object ID 2, text, ntext, or
> image node page (1:10321), slot 0, text ID 4464050176 is pointed to by
> page
> (1:10321), slot 2 and by page (1:14833), slot 3.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:14055),
> slot 8, text ID 4386324480 is referenced by page (1:24044), slot 12, but
> was
> not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:14055),
> slot 10, text ID 4386390016 is referenced by page (1:24044), slot 13, but
> was not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:14055),
> slot 11, text ID 4386455552 is referenced by page (1:24044), slot 14, but
> was not seen in the scan.
> DBCC results for 'Mydatabase_20041129'.
> DBCC results for 'sysobjects'.
> There are 677 rows in 14 pages for object 'sysobjects'.
> DBCC results for 'sysindexes'.
> The repair level on the DBCC statement caused this repair to be
> bypassed.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> The system cannot self repair this error.
> 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.
> 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.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:27801),
> slot 0, text ID 4386193408 is not referenced.
> Server: Msg 8964, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:27805),
> slot 0, text ID 4386455552 is not referenced.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:33615),
> slot 2, text ID 4385800192 is referenced by page (1:25939), slot 5, but
> was
> not seen in the scan.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:33615),
> slot 4, text ID 4385865728 is referenced by page (1:24044), slot 0, but
> was
> not seen in the scan.
> Server: Msg 8961, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:50317),
> slot 0, text ID 4366532608 does not match its reference from page
> (1:12277),
> slot 3.
> Server: Msg 8965, Level 16, State 1, Line 1
> Table error: Object ID 2. The text, ntext, or image node at page
> (1:50317),
> slot 1, text ID 4386193408 is referenced by page (1:24044), slot 5, but
> was
> not seen in the scan.
> 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.
> 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.
> There are 1029 rows in 102 pages for object 'sysindexes'.
> CHECKDB found 0 allocation errors and 21 consistency errors in table
> 'sysindexes' (object ID 2).
> DBCC results for 'syscolumns'.
> There are 2826 rows in 99 pages for object 'syscolumns'.
> DBCC results for 'systypes'.
> There are 26 rows in 1 pages for object 'systypes'.
> DBCC results for 'syscomments'.
> There are 583 rows in 171 pages for object 'syscomments'.
> DBCC results for 'sysfiles1'.
> There are 2 rows in 1 pages for object 'sysfiles1'.
> DBCC results for 'syspermissions'.
> There are 383 rows in 2 pages for object 'syspermissions'.
> DBCC results for 'sysusers'.
> There are 24 rows in 1 pages for object 'sysusers'.
> DBCC results for 'sysproperties'.
> There are 6 rows in 1 pages for object 'sysproperties'.
> DBCC results for 'sysdepends'.
> There are 4596 rows in 26 pages for object 'sysdepends'.
> DBCC results for 'sysreferences'.
> There are 59 rows in 1 pages for object 'sysreferences'.
> DBCC results for 'sysfulltextcatalogs'.
> There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
> DBCC results for 'sysfulltextnotify'.
> There are 0 rows in 0 pages for object 'sysfulltextnotify'.
> DBCC results for 'sysfilegroups'.
> There are 1 rows in 1 pages for object 'sysfilegroups'.
> DBCC results for 't_sv_look_cce_stdnt_status'.
> There are 5 rows in 1 pages for object 't_sv_look_cce_stdnt_status'.
> DBCC results for 't_sv_rpt_stdnt_icp_contact'.
> There are 3843 rows in 1179 pages for object 't_sv_rpt_stdnt_icp_contact'.
> DBCC results for 't_sv_look_sex'.
> There are 3 rows in 1 pages for object 't_sv_look_sex'.
> DBCC results for 't_sv_rpt_stdnt_pil_contact'.
> There are 867 rows in 100 pages for object 't_sv_rpt_stdnt_pil_contact'.
> DBCC results for 't_sv_app_interaction'.
> There are 5321 rows in 334 pages for object 't_sv_app_interaction'.
> DBCC results for 't_sv_app_stdnt_mktg_category'.
> There are 9 rows in 1 pages for object 't_sv_app_stdnt_mktg_category'.
> DBCC results for 't_sv_rpt_stdnt_u_ndg_contact'.
> There are 124060 rows in 3807 pages for object
> 't_sv_rpt_stdnt_u_ndg_contact'.
> DBCC results for 't_sv_look_dw_degree_level'.
> There are 488 rows in 5 pages for object 't_sv_look_dw_degree_level'.
> DBCC results for 't_sv_rpt_stdnt_g_ndg_contact'.
> There are 3171 rows in 325 pages for object
> 't_sv_rpt_stdnt_g_ndg_contact'.
> DBCC results for 't_sv_app_stdnt'.
> There are 134815 rows in 2402 pages for object 't_sv_app_stdnt'.
> DBCC results for 't_sv_look_how_contacted_type'.
> There are 5 rows in 1 pages for object 't_sv_look_how_contacted_type'.
> DBCC results for 't_sv_rpt_stdnt_all_dcp_complete'.
> There are 12376 rows in 902 pages for object
> 't_sv_rpt_stdnt_all_dcp_complete'.
> DBCC results for 't_sv_rpt_stdnt_all_contact'.
> There are 133387 rows in 2744 pages for object
> 't_sv_rpt_stdnt_all_contact'.
> DBCC results for 't_sv_app_stdnt_story_lead'.
> There are 28 rows in 3 pages for object 't_sv_app_stdnt_story_lead'.
> DBCC results for 't_sv_look_how_heard_type'.
> There are 11 rows in 1 pages for object 't_sv_look_how_heard_type'.
> DBCC results for 't_sv_temp_all_stdnts_by_sub_plan_m'.
> There are 10768 rows in 143 pages for object
> 't_sv_temp_all_stdnts_by_sub_plan_m'.
> DBCC results for 't_sv_temp_stdnt_plan_milestone_m'.
> There are 155186 rows in 1743 pages for object
> 't_sv_temp_stdnt_plan_milestone_m'.
> DBCC results for 't_sv_temp_app_stdnt_u'.
> There are 23941 rows in 209 pages for object 't_sv_temp_app_stdnt_u'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_key_words'.
> There are 9 rows in 5 pages for object
> 't_sv_rpt_mktg_stdnt_story_key_words'.
> DBCC results for 't_sv_look_dw_honors_type'.
> There are 7 rows in 1 pages for object 't_sv_look_dw_honors_type'.
> DBCC results for 'dtproperties'.
> There are 0 rows in 0 pages for object 'dtproperties'.
> DBCC results for 't_sv_temp_stdnt_demographics_m'.
> There are 130101 rows in 3428 pages for object
> 't_sv_temp_stdnt_demographics_m'.
> DBCC results for 't_sv_temp_all_stdnts_by_plan_m'.
> There are 135219 rows in 3238 pages for object
> 't_sv_temp_all_stdnts_by_plan_m'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_notes'.
> There are 0 rows in 2 pages for object 't_sv_rpt_mktg_stdnt_story_notes'.
> DBCC results for 't_sv_temp_staff_demographics_m'.
> There are 171 rows in 7 pages for object 't_sv_temp_staff_demographics_m'.
> DBCC results for 't_sv_app_staff'.
> There are 296 rows in 7 pages for object 't_sv_app_staff'.
> DBCC results for 't_sv_rpt_stdnt_bas_complete'.
> There are 2768 rows in 158 pages for object 't_sv_rpt_stdnt_bas_complete'.
> DBCC results for 't_sv_app_stdnt_mktg_note'.
> There are 0 rows in 1 pages for object 't_sv_app_stdnt_mktg_note'.
> DBCC results for 't_sv_rpt_stdnt_crt_complete'.
> There are 1758 rows in 110 pages for object 't_sv_rpt_stdnt_crt_complete'.
> DBCC results for 't_sv_look_dw_stdnt_group'.
> There are 597 rows in 5 pages for object 't_sv_look_dw_stdnt_group'.
> DBCC results for 't_sv_look_bas_application_type'.
> There are 2 rows in 1 pages for object 't_sv_look_bas_application_type'.
> DBCC results for 't_sv_app_stdnt_stdnt_group'.
> There are 91753 rows in 239 pages for object 't_sv_app_stdnt_stdnt_group'.
> DBCC results for 't_sv_look_cce_appt_type'.
> There are 9 rows in 1 pages for object 't_sv_look_cce_appt_type'.
> DBCC results for 't_sv_rpt_stdnt_acad_subplan_all'.
> There are 8459 rows in 24 pages for object
> 't_sv_rpt_stdnt_acad_subplan_all'.
> DBCC results for 't_sv_look_interpreting_language'.
> There are 8 rows in 1 pages for object 't_sv_look_interpreting_language'.
> DBCC results for 't_sv_rpt_stdnt_icp_complete'.
> There are 3843 rows in 323 pages for object 't_sv_rpt_stdnt_icp_complete'.
> DBCC results for 't_sv_admin_last_id_used'.
> There are 0 rows in 0 pages for object 't_sv_admin_last_id_used'.
> DBCC results for 't_sv_conversion_institution'.
> There are 10856 rows in 80 pages for object 't_sv_conversion_institution'.
> DBCC results for 't_sv_look_interpreting_crt_status'.
> There are 11 rows in 1 pages for object
> 't_sv_look_interpreting_crt_status'.
> DBCC results for 't_sv_rpt_stdnt_pil_complete'.
> There are 853 rows in 49 pages for object 't_sv_rpt_stdnt_pil_complete'.
> DBCC results for 't_sv_rpt_advising'.
> There are 1702 rows in 195 pages for object 't_sv_rpt_advising'.
> DBCC results for 't_sv_look_dw_degree_checkout_status'.
> There are 7 rows in 1 pages for object
> 't_sv_look_dw_degree_checkout_status'.
> DBCC results for 't_sv_look_dw_term'.
> There are 521 rows in 15 pages for object 't_sv_look_dw_term'.
> DBCC results for 't_sv_look_dw_institution'.
> There are 49024 rows in 293 pages for object 't_sv_look_dw_institution'.
> DBCC results for 't_LastIdUsed'.
> There are 1 rows in 3 pages for object 't_LastIdUsed'.
> DBCC results for 't_sv_rpt_stdnt_interpreting_crt_complete'.
> There are 409 rows in 64 pages for object
> 't_sv_rpt_stdnt_interpreting_crt_complete'.
> DBCC results for 't_sv_app_person_education_umn'.
> There are 0 rows in 1 pages for object 't_sv_app_person_education_umn'.
> DBCC results for 'ICP_ALUMNI'.
> There are 2466 rows in 217 pages for object 'ICP_ALUMNI'.
> DBCC results for 'studenR3'.
> There are 1201 rows in 91 pages for object 'studenR3'.
> DBCC results for 't_sv_app_staff_cce_plan_type'.
> There are 310 rows in 1 pages for object 't_sv_app_staff_cce_plan_type'.
> DBCC results for 'tblstudentinfo'.
> There are 129 rows in 5 pages for object 'tblstudentinfo'.
> DBCC results for 't_sv_app_stdnt_acad_progress'.
> There are 1924 rows in 7 pages for object 't_sv_app_stdnt_acad_progress'.
> DBCC results for 'Graduate_Students'.
> There are 133 rows in 6 pages for object 'Graduate_Students'.
> DBCC results for 'PreadmitStudents'.
> There are 682 rows in 77 pages for object 'PreadmitStudents'.
> DBCC results for 't_sv_admin_navigation_person_info_menu'.
> There are 18 rows in 1 pages for object
> 't_sv_admin_navigation_person_info_menu'.
> DBCC results for 't_sv_look_group'.
> There are 2 rows in 1 pages for object 't_sv_look_group'.
> DBCC results for 't_sv_rpt_person_all_contact'.
> There are 134279 rows in 2676 pages for object
> 't_sv_rpt_person_all_contact'.
> DBCC results for 't_sv_look_institution'.
> There are 278 rows in 2 pages for object 't_sv_look_institution'.
> DBCC results for 't_sv_rpt_staff_all_contact'.
> There are 259 rows in 12 pages for object 't_sv_rpt_staff_all_contact'.
> DBCC results for 't_sv_admin_navigation_acad_plan_info_menu'.
> There are 4 rows in 1 pages for object
> 't_sv_admin_navigation_acad_plan_info_menu'.
> DBCC results for 't_sv_look_degree_level'.
> There are 11 rows in 1 pages for object 't_sv_look_degree_level'.
> DBCC results for 't_sv_app_stdnt_plan'.
> There are 140747 rows in 3006 pages for object 't_sv_app_stdnt_plan'.
> DBCC results for 't_sv_app_stdnt_staff'.
> There are 1713 rows in 19 pages for object 't_sv_app_stdnt_staff'.
> DBCC results for 't_sv_rpt_staff_by_program_contact'.
> There are 246 rows in 25 pages for object
> 't_sv_rpt_staff_by_program_contact'.
> DBCC results for 'studenR3_old'.
> There are 1372 rows in 116 pages for object 'studenR3_old'.
> DBCC results for 't_sv_rpt_stdnt_international_complete'.
> There are 472 rows in 25 pages for object
> 't_sv_rpt_stdnt_international_complete'.
> DBCC results for 't_sv_app_person_education'.
> There are 1685 rows in 10 pages for object 't_sv_app_person_education'.
> DBCC results for 't_sv_app_stdnt_mls'.
> There are 3215 rows in 18 pages for object 't_sv_app_stdnt_mls'.
> DBCC results for 't_sv_look_dw_staff_level'.
> There are 108 rows in 1 pages for object 't_sv_look_dw_staff_level'.
> DBCC results for 't_sv_rpt_mls_mailing'.
> There are 471 rows in 8 pages for object 't_sv_rpt_mls_mailing'.
> DBCC results for 't_sv_look_addr_type'.
> There are 4 rows in 1 pages for object 't_sv_look_addr_type'.
> DBCC results for 't_sv_rpt_stdnt_mls_contact'.
> There are 3140 rows in 98 pages for object 't_sv_rpt_stdnt_mls_contact'.
> DBCC results for 't_sv_look_milestone'.
> There are 22 rows in 1 pages for object 't_sv_look_milestone'.
> DBCC results for 'PreadmitStudents_old'.
> There are 664 rows in 72 pages for object 'PreadmitStudents_old'.
> DBCC results for 't_sv_look_dw_prog_status'.
> There are 12 rows in 4 pages for object 't_sv_look_dw_prog_status'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_contact_info'.
> There are 14 rows in 5 pages for object
> 't_sv_rpt_mktg_stdnt_story_contact_info'.
> DBCC results for 't_sv_app_stdnt_plan_milestone'.
> There are 157105 rows in 912 pages for object
> 't_sv_app_stdnt_plan_milestone'.
> DBCC results for 't_sv_look_dw_ethnic_group'.
> There are 7 rows in 4 pages for object 't_sv_look_dw_ethnic_group'.
> DBCC results for 't_sv_rpt_stdnt_mls_complete'.
> There are 3140 rows in 209 pages for object 't_sv_rpt_stdnt_mls_complete'.
> DBCC results for 't_sv_look_dw_dir_exclude'.
> There are 7 rows in 4 pages for object 't_sv_look_dw_dir_exclude'.
> DBCC results for 't_sv_look_dw_acad_prog'.
> There are 53 rows in 7 pages for object 't_sv_look_dw_acad_prog'.
> DBCC results for 't_sv_rpt_mktg_stdnt_story_lead_info'.
> There are 28 rows in 7 pages for object
> 't_sv_rpt_mktg_stdnt_story_lead_info'.
> DBCC results for 't_sv_look_dw_acad_plan'.
> There are 99 rows in 11 pages for object 't_sv_look_dw_acad_plan'.
> DBCC results for 'ICP_ALUMNI_old'.
> There are 2358 rows in 205 pages for object 'ICP_ALUMNI_old'.
> DBCC results for 't_sv_app_person'.
> There are 135045 rows in 2089 pages for object 't_sv_app_person'.
> DBCC results for 't_sv_app_stdnt_icp'.
> There are 3864 rows in 16 pages for object 't_sv_app_stdnt_icp'.
> DBCC results for 'icp_term_conversion'.
> There are 120 rows in 1 pages for object 'icp_term_conversion'.
> DBCC results for 't_sv_look_interaction_type'.
> There are 6 rows in 1 pages for object 't_sv_look_interaction_type'.
> DBCC results for 'studenR3_062404'.
> There are 1391 rows in 124 pages for object 'studenR3_062404'.
> DBCC results for 't_sv_rpt_stdnt_notes'.
> There are 5251 rows in 428 pages for object 't_sv_rpt_stdnt_notes'.
> DBCC results for 't_sv_rpt_stdnt_crt_contact'.
> There are 1758 rows in 84 pages for object 't_sv_rpt_stdnt_crt_contact'.
> DBCC results for 'ICP_ALUMNI_06242004'.
> There are 2346 rows in 213 pages for object 'ICP_ALUMNI_06242004'.
> DBCC results for 't_sv_app_stdnt_pil'.
> There are 868 rows in 6 pages for object 't_sv_app_stdnt_pil'.
> DBCC results for 't_sv_look_interaction_location_type'.
> There are 4 rows in 1 pages for object
> 't_sv_look_interaction_location_type'.
> DBCC results for 't_sv_app_stdnt_crt'.
> There are 1798 rows in 10 pages for object 't_sv_app_stdnt_crt'.
> DBCC results for 't_sv_look_mktg_category'.
> There are 10 rows in 1 pages for object 't_sv_look_mktg_category'.
> DBCC results for 't_sv_look_phone_type'.
> There are 7 rows in 1 pages for object 't_sv_look_phone_type'.
> DBCC results for 'PIL_area_specialists'.
> There are 119 rows in 1 pages for object 'PIL_area_specialists'.
> DBCC results for 't_sv_look_stdnt_story_lead'.
> There are 5 rows in 1 pages for object 't_sv_look_stdnt_story_lead'.
> DBCC results for 't_sv_look_cce_stdnt_status_sub'.
> There are 18 rows in 1 pages for object 't_sv_look_cce_stdnt_status_sub'.
> DBCC results for 't_sv_look_mktg_contact_type'.
> There are 2 rows in 1 pages for object 't_sv_look_mktg_contact_type'.
> DBCC results for 't_sv_admin_archive_plan_term_status'.
> There are 0 rows in 0 pages for object
> 't_sv_admin_archive_plan_term_status'.
> DBCC results for 't_sv_app_person_addr'.
> There are 190774 rows in 1748 pages for object 't_sv_app_person_addr'.
> DBCC results for 't_sv_look_email_type'.
> There are 5 rows in 1 pages for object 't_sv_look_email_type'.
> DBCC results for 't_sv_look_dw_subplan'.
> There are 409 rows in 3 pages for object 't_sv_look_dw_subplan'.
> DBCC results for 't_sv_app_person_email'.
> There are 81864 rows in 547 pages for object 't_sv_app_person_email'.
> DBCC results for 't_sv_app_person_phone'.
> There are 106574 rows in 612 pages for object 't_sv_app_person_phone'.
> DBCC results for 't_sv_app_stdnt_bas'.
> There are 2797 rows in 7 pages for object 't_sv_app_stdnt_bas'.
> DBCC results for 't_sv_look_dw_acad_progress_type'.
> There are 8 rows in 1 pages for object 't_sv_look_dw_acad_progress_type'.
> DBCC results for 'PreadmitStudents_07142004'.
> There are 684 rows in 154 pages for object 'PreadmitStudents_07142004'.
> DBCC results for 't_sv_app_stdnt_interpreting_crt'.
> There are 292 rows in 4 pages for object
> 't_sv_app_stdnt_interpreting_crt'.
> DBCC results for 'tblstudentinfo_07142004'.
> There are 140 rows in 6 pages for object 'tblstudentinfo_07142004'.
> DBCC results for 't_sv_look_employer'.
> There are 798 rows in 4 pages for object 't_sv_look_employer'.
> DBCC results for 't_sv_app_person_group'.
> There are 38 rows in 1 pages for object 't_sv_app_person_group'.
> DBCC results for 'preadmit_pil_staff_logins'.
> There are 7 rows in 1 pages for object 'preadmit_pil_staff_logins'.
> DBCC results for 't_sv_look_occupation_category'.
> There are 31 rows in 1 pages for object 't_sv_look_occupation_category'.
> DBCC results for 'Graduate_Students_07152004'.
> There are 130 rows in 6 pages for object 'Graduate_Students_07152004'.
> DBCC results for 't_sv_admin_history'.
> There are 4640 rows in 46 pages for object 't_sv_admin_history'.
> DBCC results for 't_sv_rpt_stdnt_bas_contact'.
> There are 2768 rows in 222 pages for object 't_sv_rpt_stdnt_bas_contact'.
> DBCC results for 't_sv_app_stdnt_plan_subplan'.
> There are 10037 rows in 48 pages for object 't_sv_app_stdnt_plan_subplan'.
> DBCC results for 't_sv_look_cce_plan_type'.
> There are 8 rows in 1 pages for object 't_sv_look_cce_plan_type'.
> DBCC results for 'icp_advisor_lookup'.
> There are 6 rows in 1 pages for object 'icp_advisor_lookup'.
> CHECKDB found 0 allocation errors and 21 consistency errors in database
> 'Mydatabase_20041129'.
> DBCC execution completed. If DBCC printed error messages, contact your
> system administrator.
>|||As Andrew says, restore is your best option for all corruptions. You should
also analyze your system to see what caused the problems.
In fact, in this case, restore is your only option as the corruptions are in
sysindexes and cannot be repaired.
You should contact PSS to help you.
Regards.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:eS#4oFl1EHA.1652@.TK2MSFTNGP11.phx.gbl...
> If the db is that badly damaged your best bet is to call MS PSS and see
what
> they can do. In any case your best option with damage sucha s that is to
> restore from the last good backup.
>
> http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
> http://www.mssqlserver.com/faq/general-pss.asp MS PSS
> --
> Andrew J. Kelly SQL MVP
>
> "Mark" <Mark@.nowhere.com> wrote in message
> news:%23k31Qok1EHA.1260@.TK2MSFTNGP12.phx.gbl...
> > SQL Server 2000 SP 3 (8.00.818), Windows 2003 Server, 2 processors, 1 GB
> > of
> > RAM
> >
> > We have a 400 MB database that started having 7102 and 7105 Fatal errors
> > today when using simple select statments and drop table commands. An
> > example
> > error message is below:
> >
> > Server: Msg 21, Level 20, State 1, Line 1
> > Warning: Fatal error 7102 occurred at Nov 29 2004 11:41AM
> >
> > The event log does not provide a lot more detail:
> >
> > DESCRIPTION: Error: 7102, Severity: 20, State: 7
> > SQL Server Internal Error. Text manager cannot continue with current
> > statement.
> >
> > We tried using DBCC Checkdb, and found quite a few issues. We then ran
> > the
> > following in single user mode:
> >
> > DBCC Checkdb (Mydatabase_20041129, REPAIR_ALLOW_DATA_LOSS)
> >
> > This resulted in the massive output below and suggests that some errors
> > could not be fixed. I noticed several references to "text, ntext, or
> > image". There is only 1 of those datatypes in any of the databases
> > columns,
> > and that is an image datatype in the dtproperties table, which we
> > certainly
> > have not messed with. What is the next logical way of attempting to
> > resolve
> > this issue?
> >
> > Thanks in advance! We really appreciate it.
> >
> > Mark
> >
> >
> >
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4464050176 owned by data record
> > identified by RID = (1:80:6) id = 304056169 and indid = 5.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 2982150144 owned by data record
> > identified by RID = (1:1527:1) id = 2130822653 and indid = 2.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4385865728 owned by data record
> > identified by RID = (1:24044:0) id = 224055884 and indid = 5.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4386127872 owned by data record
> > identified by RID = (1:24044:4) id = 224055884 and indid = 9.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4386193408 owned by data record
> > identified by RID = (1:24044:5) id = 224055884 and indid = 10.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4386324480 owned by data record
> > identified by RID = (1:24044:12) id = 240055941 and indid = 6.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4386390016 owned by data record
> > identified by RID = (1:24044:13) id = 240055941 and indid = 7.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4386455552 owned by data record
> > identified by RID = (1:24044:14) id = 240055941 and indid = 8.
> > Server: Msg 8929, Level 16, State 1, Line 1
> > Object ID 2: Errors found in text ID 4385800192 owned by data record
> > identified by RID = (1:25939:5) id = 224055884 and indid = 4.
> > Server: Msg 8964, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
(1:6722),
> > slot 0, text ID 2982150144 is not referenced.
> > Server: Msg 8961, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:10321),
> > slot 0, text ID 4464050176 does not match its reference from page
> > (1:14833),
> > slot 3.
> > Server: Msg 8974, Level 16, State 1, Line 1
> > Text node referenced by more than one node. Object ID 2, text, ntext, or
> > image node page (1:10321), slot 0, text ID 4464050176 is pointed to by
> > page
> > (1:10321), slot 2 and by page (1:14833), slot 3.
> > Server: Msg 8965, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:14055),
> > slot 8, text ID 4386324480 is referenced by page (1:24044), slot 12, but
> > was
> > not seen in the scan.
> > Server: Msg 8965, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:14055),
> > slot 10, text ID 4386390016 is referenced by page (1:24044), slot 13,
but
> > was not seen in the scan.
> > Server: Msg 8965, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:14055),
> > slot 11, text ID 4386455552 is referenced by page (1:24044), slot 14,
but
> > was not seen in the scan.
> > DBCC results for 'Mydatabase_20041129'.
> > DBCC results for 'sysobjects'.
> > There are 677 rows in 14 pages for object 'sysobjects'.
> > DBCC results for 'sysindexes'.
> > The repair level on the DBCC statement caused this repair to be
> > bypassed.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > The system cannot self repair this error.
> > 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.
> > 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.
> > Server: Msg 8964, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:27801),
> > slot 0, text ID 4386193408 is not referenced.
> > Server: Msg 8964, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:27805),
> > slot 0, text ID 4386455552 is not referenced.
> > Server: Msg 8965, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:33615),
> > slot 2, text ID 4385800192 is referenced by page (1:25939), slot 5, but
> > was
> > not seen in the scan.
> > Server: Msg 8965, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:33615),
> > slot 4, text ID 4385865728 is referenced by page (1:24044), slot 0, but
> > was
> > not seen in the scan.
> > Server: Msg 8961, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:50317),
> > slot 0, text ID 4366532608 does not match its reference from page
> > (1:12277),
> > slot 3.
> > Server: Msg 8965, Level 16, State 1, Line 1
> > Table error: Object ID 2. The text, ntext, or image node at page
> > (1:50317),
> > slot 1, text ID 4386193408 is referenced by page (1:24044), slot 5, but
> > was
> > not seen in the scan.
> > 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.
> > 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.
> > There are 1029 rows in 102 pages for object 'sysindexes'.
> > CHECKDB found 0 allocation errors and 21 consistency errors in table
> > 'sysindexes' (object ID 2).
> > DBCC results for 'syscolumns'.
> > There are 2826 rows in 99 pages for object 'syscolumns'.
> > DBCC results for 'systypes'.
> > There are 26 rows in 1 pages for object 'systypes'.
> > DBCC results for 'syscomments'.
> > There are 583 rows in 171 pages for object 'syscomments'.
> > DBCC results for 'sysfiles1'.
> > There are 2 rows in 1 pages for object 'sysfiles1'.
> > DBCC results for 'syspermissions'.
> > There are 383 rows in 2 pages for object 'syspermissions'.
> > DBCC results for 'sysusers'.
> > There are 24 rows in 1 pages for object 'sysusers'.
> > DBCC results for 'sysproperties'.
> > There are 6 rows in 1 pages for object 'sysproperties'.
> > DBCC results for 'sysdepends'.
> > There are 4596 rows in 26 pages for object 'sysdepends'.
> > DBCC results for 'sysreferences'.
> > There are 59 rows in 1 pages for object 'sysreferences'.
> > DBCC results for 'sysfulltextcatalogs'.
> > There are 0 rows in 0 pages for object 'sysfulltextcatalogs'.
> > DBCC results for 'sysfulltextnotify'.
> > There are 0 rows in 0 pages for object 'sysfulltextnotify'.
> > DBCC results for 'sysfilegroups'.
> > There are 1 rows in 1 pages for object 'sysfilegroups'.
> > DBCC results for 't_sv_look_cce_stdnt_status'.
> > There are 5 rows in 1 pages for object 't_sv_look_cce_stdnt_status'.
> > DBCC results for 't_sv_rpt_stdnt_icp_contact'.
> > There are 3843 rows in 1179 pages for object
't_sv_rpt_stdnt_icp_contact'.
> > DBCC results for 't_sv_look_sex'.
> > There are 3 rows in 1 pages for object 't_sv_look_sex'.
> > DBCC results for 't_sv_rpt_stdnt_pil_contact'.
> > There are 867 rows in 100 pages for object 't_sv_rpt_stdnt_pil_contact'.
> > DBCC results for 't_sv_app_interaction'.
> > There are 5321 rows in 334 pages for object 't_sv_app_interaction'.
> > DBCC results for 't_sv_app_stdnt_mktg_category'.
> > There are 9 rows in 1 pages for object 't_sv_app_stdnt_mktg_category'.
> > DBCC results for 't_sv_rpt_stdnt_u_ndg_contact'.
> > There are 124060 rows in 3807 pages for object
> > 't_sv_rpt_stdnt_u_ndg_contact'.
> > DBCC results for 't_sv_look_dw_degree_level'.
> > There are 488 rows in 5 pages for object 't_sv_look_dw_degree_level'.
> > DBCC results for 't_sv_rpt_stdnt_g_ndg_contact'.
> > There are 3171 rows in 325 pages for object
> > 't_sv_rpt_stdnt_g_ndg_contact'.
> > DBCC results for 't_sv_app_stdnt'.
> > There are 134815 rows in 2402 pages for object 't_sv_app_stdnt'.
> > DBCC results for 't_sv_look_how_contacted_type'.
> > There are 5 rows in 1 pages for object 't_sv_look_how_contacted_type'.
> > DBCC results for 't_sv_rpt_stdnt_all_dcp_complete'.
> > There are 12376 rows in 902 pages for object
> > 't_sv_rpt_stdnt_all_dcp_complete'.
> > DBCC results for 't_sv_rpt_stdnt_all_contact'.
> > There are 133387 rows in 2744 pages for object
> > 't_sv_rpt_stdnt_all_contact'.
> > DBCC results for 't_sv_app_stdnt_story_lead'.
> > There are 28 rows in 3 pages for object 't_sv_app_stdnt_story_lead'.
> > DBCC results for 't_sv_look_how_heard_type'.
> > There are 11 rows in 1 pages for object 't_sv_look_how_heard_type'.
> > DBCC results for 't_sv_temp_all_stdnts_by_sub_plan_m'.
> > There are 10768 rows in 143 pages for object
> > 't_sv_temp_all_stdnts_by_sub_plan_m'.
> > DBCC results for 't_sv_temp_stdnt_plan_milestone_m'.
> > There are 155186 rows in 1743 pages for object
> > 't_sv_temp_stdnt_plan_milestone_m'.
> > DBCC results for 't_sv_temp_app_stdnt_u'.
> > There are 23941 rows in 209 pages for object 't_sv_temp_app_stdnt_u'.
> > DBCC results for 't_sv_rpt_mktg_stdnt_story_key_words'.
> > There are 9 rows in 5 pages for object
> > 't_sv_rpt_mktg_stdnt_story_key_words'.
> > DBCC results for 't_sv_look_dw_honors_type'.
> > There are 7 rows in 1 pages for object 't_sv_look_dw_honors_type'.
> > DBCC results for 'dtproperties'.
> > There are 0 rows in 0 pages for object 'dtproperties'.
> > DBCC results for 't_sv_temp_stdnt_demographics_m'.
> > There are 130101 rows in 3428 pages for object
> > 't_sv_temp_stdnt_demographics_m'.
> > DBCC results for 't_sv_temp_all_stdnts_by_plan_m'.
> > There are 135219 rows in 3238 pages for object
> > 't_sv_temp_all_stdnts_by_plan_m'.
> > DBCC results for 't_sv_rpt_mktg_stdnt_story_notes'.
> > There are 0 rows in 2 pages for object
't_sv_rpt_mktg_stdnt_story_notes'.
> > DBCC results for 't_sv_temp_staff_demographics_m'.
> > There are 171 rows in 7 pages for object
't_sv_temp_staff_demographics_m'.
> > DBCC results for 't_sv_app_staff'.
> > There are 296 rows in 7 pages for object 't_sv_app_staff'.
> > DBCC results for 't_sv_rpt_stdnt_bas_complete'.
> > There are 2768 rows in 158 pages for object
't_sv_rpt_stdnt_bas_complete'.
> > DBCC results for 't_sv_app_stdnt_mktg_note'.
> > There are 0 rows in 1 pages for object 't_sv_app_stdnt_mktg_note'.
> > DBCC results for 't_sv_rpt_stdnt_crt_complete'.
> > There are 1758 rows in 110 pages for object
't_sv_rpt_stdnt_crt_complete'.
> > DBCC results for 't_sv_look_dw_stdnt_group'.
> > There are 597 rows in 5 pages for object 't_sv_look_dw_stdnt_group'.
> > DBCC results for 't_sv_look_bas_application_type'.
> > There are 2 rows in 1 pages for object 't_sv_look_bas_application_type'.
> > DBCC results for 't_sv_app_stdnt_stdnt_group'.
> > There are 91753 rows in 239 pages for object
't_sv_app_stdnt_stdnt_group'.
> > DBCC results for 't_sv_look_cce_appt_type'.
> > There are 9 rows in 1 pages for object 't_sv_look_cce_appt_type'.
> > DBCC results for 't_sv_rpt_stdnt_acad_subplan_all'.
> > There are 8459 rows in 24 pages for object
> > 't_sv_rpt_stdnt_acad_subplan_all'.
> > DBCC results for 't_sv_look_interpreting_language'.
> > There are 8 rows in 1 pages for object
't_sv_look_interpreting_language'.
> > DBCC results for 't_sv_rpt_stdnt_icp_complete'.
> > There are 3843 rows in 323 pages for object
't_sv_rpt_stdnt_icp_complete'.
> > DBCC results for 't_sv_admin_last_id_used'.
> > There are 0 rows in 0 pages for object 't_sv_admin_last_id_used'.
> > DBCC results for 't_sv_conversion_institution'.
> > There are 10856 rows in 80 pages for object
't_sv_conversion_institution'.
> > DBCC results for 't_sv_look_interpreting_crt_status'.
> > There are 11 rows in 1 pages for object
> > 't_sv_look_interpreting_crt_status'.
> > DBCC results for 't_sv_rpt_stdnt_pil_complete'.
> > There are 853 rows in 49 pages for object 't_sv_rpt_stdnt_pil_complete'.
> > DBCC results for 't_sv_rpt_advising'.
> > There are 1702 rows in 195 pages for object 't_sv_rpt_advising'.
> > DBCC results for 't_sv_look_dw_degree_checkout_status'.
> > There are 7 rows in 1 pages for object
> > 't_sv_look_dw_degree_checkout_status'.
> > DBCC results for 't_sv_look_dw_term'.
> > There are 521 rows in 15 pages for object 't_sv_look_dw_term'.
> > DBCC results for 't_sv_look_dw_institution'.
> > There are 49024 rows in 293 pages for object 't_sv_look_dw_institution'.
> > DBCC results for 't_LastIdUsed'.
> > There are 1 rows in 3 pages for object 't_LastIdUsed'.
> > DBCC results for 't_sv_rpt_stdnt_interpreting_crt_complete'.
> > There are 409 rows in 64 pages for object
> > 't_sv_rpt_stdnt_interpreting_crt_complete'.
> > DBCC results for 't_sv_app_person_education_umn'.
> > There are 0 rows in 1 pages for object 't_sv_app_person_education_umn'.
> > DBCC results for 'ICP_ALUMNI'.
> > There are 2466 rows in 217 pages for object 'ICP_ALUMNI'.
> > DBCC results for 'studenR3'.
> > There are 1201 rows in 91 pages for object 'studenR3'.
> > DBCC results for 't_sv_app_staff_cce_plan_type'.
> > There are 310 rows in 1 pages for object 't_sv_app_staff_cce_plan_type'.
> > DBCC results for 'tblstudentinfo'.
> > There are 129 rows in 5 pages for object 'tblstudentinfo'.
> > DBCC results for 't_sv_app_stdnt_acad_progress'.
> > There are 1924 rows in 7 pages for object
't_sv_app_stdnt_acad_progress'.
> > DBCC results for 'Graduate_Students'.
> > There are 133 rows in 6 pages for object 'Graduate_Students'.
> > DBCC results for 'PreadmitStudents'.
> > There are 682 rows in 77 pages for object 'PreadmitStudents'.
> > DBCC results for 't_sv_admin_navigation_person_info_menu'.
> > There are 18 rows in 1 pages for object
> > 't_sv_admin_navigation_person_info_menu'.
> > DBCC results for 't_sv_look_group'.
> > There are 2 rows in 1 pages for object 't_sv_look_group'.
> > DBCC results for 't_sv_rpt_person_all_contact'.
> > There are 134279 rows in 2676 pages for object
> > 't_sv_rpt_person_all_contact'.
> > DBCC results for 't_sv_look_institution'.
> > There are 278 rows in 2 pages for object 't_sv_look_institution'.
> > DBCC results for 't_sv_rpt_staff_all_contact'.
> > There are 259 rows in 12 pages for object 't_sv_rpt_staff_all_contact'.
> > DBCC results for 't_sv_admin_navigation_acad_plan_info_menu'.
> > There are 4 rows in 1 pages for object
> > 't_sv_admin_navigation_acad_plan_info_menu'.
> > DBCC results for 't_sv_look_degree_level'.
> > There are 11 rows in 1 pages for object 't_sv_look_degree_level'.
> > DBCC results for 't_sv_app_stdnt_plan'.
> > There are 140747 rows in 3006 pages for object 't_sv_app_stdnt_plan'.
> > DBCC results for 't_sv_app_stdnt_staff'.
> > There are 1713 rows in 19 pages for object 't_sv_app_stdnt_staff'.
> > DBCC results for 't_sv_rpt_staff_by_program_contact'.
> > There are 246 rows in 25 pages for object
> > 't_sv_rpt_staff_by_program_contact'.
> > DBCC results for 'studenR3_old'.
> > There are 1372 rows in 116 pages for object 'studenR3_old'.
> > DBCC results for 't_sv_rpt_stdnt_international_complete'.
> > There are 472 rows in 25 pages for object
> > 't_sv_rpt_stdnt_international_complete'.
> > DBCC results for 't_sv_app_person_education'.
> > There are 1685 rows in 10 pages for object 't_sv_app_person_education'.
> > DBCC results for 't_sv_app_stdnt_mls'.
> > There are 3215 rows in 18 pages for object 't_sv_app_stdnt_mls'.
> > DBCC results for 't_sv_look_dw_staff_level'.
> > There are 108 rows in 1 pages for object 't_sv_look_dw_staff_level'.
> > DBCC results for 't_sv_rpt_mls_mailing'.
> > There are 471 rows in 8 pages for object 't_sv_rpt_mls_mailing'.
> > DBCC results for 't_sv_look_addr_type'.
> > There are 4 rows in 1 pages for object 't_sv_look_addr_type'.
> > DBCC results for 't_sv_rpt_stdnt_mls_contact'.
> > There are 3140 rows in 98 pages for object 't_sv_rpt_stdnt_mls_contact'.
> > DBCC results for 't_sv_look_milestone'.
> > There are 22 rows in 1 pages for object 't_sv_look_milestone'.
> > DBCC results for 'PreadmitStudents_old'.
> > There are 664 rows in 72 pages for object 'PreadmitStudents_old'.
> > DBCC results for 't_sv_look_dw_prog_status'.
> > There are 12 rows in 4 pages for object 't_sv_look_dw_prog_status'.
> > DBCC results for 't_sv_rpt_mktg_stdnt_story_contact_info'.
> > There are 14 rows in 5 pages for object
> > 't_sv_rpt_mktg_stdnt_story_contact_info'.
> > DBCC results for 't_sv_app_stdnt_plan_milestone'.
> > There are 157105 rows in 912 pages for object
> > 't_sv_app_stdnt_plan_milestone'.
> > DBCC results for 't_sv_look_dw_ethnic_group'.
> > There are 7 rows in 4 pages for object 't_sv_look_dw_ethnic_group'.
> > DBCC results for 't_sv_rpt_stdnt_mls_complete'.
> > There are 3140 rows in 209 pages for object
't_sv_rpt_stdnt_mls_complete'.
> > DBCC results for 't_sv_look_dw_dir_exclude'.
> > There are 7 rows in 4 pages for object 't_sv_look_dw_dir_exclude'.
> > DBCC results for 't_sv_look_dw_acad_prog'.
> > There are 53 rows in 7 pages for object 't_sv_look_dw_acad_prog'.
> > DBCC results for 't_sv_rpt_mktg_stdnt_story_lead_info'.
> > There are 28 rows in 7 pages for object
> > 't_sv_rpt_mktg_stdnt_story_lead_info'.
> > DBCC results for 't_sv_look_dw_acad_plan'.
> > There are 99 rows in 11 pages for object 't_sv_look_dw_acad_plan'.
> > DBCC results for 'ICP_ALUMNI_old'.
> > There are 2358 rows in 205 pages for object 'ICP_ALUMNI_old'.
> > DBCC results for 't_sv_app_person'.
> > There are 135045 rows in 2089 pages for object 't_sv_app_person'.
> > DBCC results for 't_sv_app_stdnt_icp'.
> > There are 3864 rows in 16 pages for object 't_sv_app_stdnt_icp'.
> > DBCC results for 'icp_term_conversion'.
> > There are 120 rows in 1 pages for object 'icp_term_conversion'.
> > DBCC results for 't_sv_look_interaction_type'.
> > There are 6 rows in 1 pages for object 't_sv_look_interaction_type'.
> > DBCC results for 'studenR3_062404'.
> > There are 1391 rows in 124 pages for object 'studenR3_062404'.
> > DBCC results for 't_sv_rpt_stdnt_notes'.
> > There are 5251 rows in 428 pages for object 't_sv_rpt_stdnt_notes'.
> > DBCC results for 't_sv_rpt_stdnt_crt_contact'.
> > There are 1758 rows in 84 pages for object 't_sv_rpt_stdnt_crt_contact'.
> > DBCC results for 'ICP_ALUMNI_06242004'.
> > There are 2346 rows in 213 pages for object 'ICP_ALUMNI_06242004'.
> > DBCC results for 't_sv_app_stdnt_pil'.
> > There are 868 rows in 6 pages for object 't_sv_app_stdnt_pil'.
> > DBCC results for 't_sv_look_interaction_location_type'.
> > There are 4 rows in 1 pages for object
> > 't_sv_look_interaction_location_type'.
> > DBCC results for 't_sv_app_stdnt_crt'.
> > There are 1798 rows in 10 pages for object 't_sv_app_stdnt_crt'.
> > DBCC results for 't_sv_look_mktg_category'.
> > There are 10 rows in 1 pages for object 't_sv_look_mktg_category'.
> > DBCC results for 't_sv_look_phone_type'.
> > There are 7 rows in 1 pages for object 't_sv_look_phone_type'.
> > DBCC results for 'PIL_area_specialists'.
> > There are 119 rows in 1 pages for object 'PIL_area_specialists'.
> > DBCC results for 't_sv_look_stdnt_story_lead'.
> > There are 5 rows in 1 pages for object 't_sv_look_stdnt_story_lead'.
> > DBCC results for 't_sv_look_cce_stdnt_status_sub'.
> > There are 18 rows in 1 pages for object
't_sv_look_cce_stdnt_status_sub'.
> > DBCC results for 't_sv_look_mktg_contact_type'.
> > There are 2 rows in 1 pages for object 't_sv_look_mktg_contact_type'.
> > DBCC results for 't_sv_admin_archive_plan_term_status'.
> > There are 0 rows in 0 pages for object
> > 't_sv_admin_archive_plan_term_status'.
> > DBCC results for 't_sv_app_person_addr'.
> > There are 190774 rows in 1748 pages for object 't_sv_app_person_addr'.
> > DBCC results for 't_sv_look_email_type'.
> > There are 5 rows in 1 pages for object 't_sv_look_email_type'.
> > DBCC results for 't_sv_look_dw_subplan'.
> > There are 409 rows in 3 pages for object 't_sv_look_dw_subplan'.
> > DBCC results for 't_sv_app_person_email'.
> > There are 81864 rows in 547 pages for object 't_sv_app_person_email'.
> > DBCC results for 't_sv_app_person_phone'.
> > There are 106574 rows in 612 pages for object 't_sv_app_person_phone'.
> > DBCC results for 't_sv_app_stdnt_bas'.
> > There are 2797 rows in 7 pages for object 't_sv_app_stdnt_bas'.
> > DBCC results for 't_sv_look_dw_acad_progress_type'.
> > There are 8 rows in 1 pages for object
't_sv_look_dw_acad_progress_type'.
> > DBCC results for 'PreadmitStudents_07142004'.
> > There are 684 rows in 154 pages for object 'PreadmitStudents_07142004'.
> > DBCC results for 't_sv_app_stdnt_interpreting_crt'.
> > There are 292 rows in 4 pages for object
> > 't_sv_app_stdnt_interpreting_crt'.
> > DBCC results for 'tblstudentinfo_07142004'.
> > There are 140 rows in 6 pages for object 'tblstudentinfo_07142004'.
> > DBCC results for 't_sv_look_employer'.
> > There are 798 rows in 4 pages for object 't_sv_look_employer'.
> > DBCC results for 't_sv_app_person_group'.
> > There are 38 rows in 1 pages for object 't_sv_app_person_group'.
> > DBCC results for 'preadmit_pil_staff_logins'.
> > There are 7 rows in 1 pages for object 'preadmit_pil_staff_logins'.
> > DBCC results for 't_sv_look_occupation_category'.
> > There are 31 rows in 1 pages for object 't_sv_look_occupation_category'.
> > DBCC results for 'Graduate_Students_07152004'.
> > There are 130 rows in 6 pages for object 'Graduate_Students_07152004'.
> > DBCC results for 't_sv_admin_history'.
> > There are 4640 rows in 46 pages for object 't_sv_admin_history'.
> > DBCC results for 't_sv_rpt_stdnt_bas_contact'.
> > There are 2768 rows in 222 pages for object
't_sv_rpt_stdnt_bas_contact'.
> > DBCC results for 't_sv_app_stdnt_plan_subplan'.
> > There are 10037 rows in 48 pages for object
't_sv_app_stdnt_plan_subplan'.
> > DBCC results for 't_sv_look_cce_plan_type'.
> > There are 8 rows in 1 pages for object 't_sv_look_cce_plan_type'.
> > DBCC results for 'icp_advisor_lookup'.
> > There are 6 rows in 1 pages for object 'icp_advisor_lookup'.
> > CHECKDB found 0 allocation errors and 21 consistency errors in database
> > 'Mydatabase_20041129'.
> > DBCC execution completed. If DBCC printed error messages, contact your
> > system administrator.
> >
> >
>