|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, April 18, 2013 3:09 AM
Points: 167,
Visits: 440
|
|
| Ohh.. Is there any way to know how much data lost? Or how to find what table affected by that ?
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
jitendra.padhiyar (1/15/2013) Ohh.. Is there any way to know how much data lost? Or how to find what table affected by that ?
How much, no, not after the fact. Which table, yes. The tables PTJOBOPHISTORY and PTJOBLOGS
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
Mr or Mrs. 500
      
Group: General Forum Members
Last Login: Monday, May 06, 2013 5:58 AM
Points: 535,
Visits: 1,010
|
|
Before you go further down this rabbit hole, do you have backups of this database? It may be better to restore from full/logs before proceeding.
I hope those backups you removed to clear up space on the drive were not from the database you are working on. If they were I hope they were moved and not deleted...
Joie Andrew "Since 1982"
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, April 18, 2013 3:09 AM
Points: 167,
Visits: 440
|
|
Thanks a lot GilaMonster and Joe !
I just checked with client end, and found they are ok with the performance of sql server but... they got one error while performing Delete operation with PTJOBLOGS.. (:
The were trying to perform below delete operation:
DELETE FROM PTPortalUser.PTJOBLOGS WHERE INSTANCEID < 614469
and got error message:
Msg 8908, Level 22, State 6, Line 1 Table error: Database ID 23, object ID 901578250, index ID 0. Chain linkage mismatch. (1:753306)->next = (1:753307), but (1:753307)->prev = (1:706408).
It seems its consistency error that Checkdb was not able to repair. Should I run checkdb again with All_ErrorMSGS ? to know whts going on ? OR any other way to cope with this error ? Indexid=0 seems cluster index issue..
|
|
|
|
|
SSC-Enthusiastic
      
Group: General Forum Members
Last Login: Thursday, April 18, 2013 3:09 AM
Points: 167,
Visits: 440
|
|
Just googled error message and found this issue occurs because the SHRINK operation cannot remove a page from the SYSFILES1 system table on the primary data file of the database. And we can fix it by applying latest service pack of SQL Server 2000!!
Is it advisable ?? Please help me masters...!
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 6:43 AM
Points: 1,785,
Visits: 1,008
|
|
index id 0 is heap , just to get a better idea for future use. did u get this error after a power failure ? Did you try running a checkdsk on the disk drives?
@Gail , would it make sense now to add a clustered index or rebuild the clustered index ?
Jayanth Kurup
|
|
|
|
|
SSCommitted
      
Group: General Forum Members
Last Login: Tuesday, May 07, 2013 6:43 AM
Points: 1,785,
Visits: 1,008
|
|
I wouldnt start adding service packs ( sql 2000 and still ahve serice packs you need to add??) to fix a issue your facing now. Applying service packs need to be thought out properly.
Are you able to access the table , can you create a copy of the table ?
Jayanth Kurup
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
jitendra.padhiyar (1/15/2013)
The were trying to perform below delete operation:
DELETE FROM PTPortalUser.PTJOBLOGS WHERE INSTANCEID < 614469
and got error message:
Msg 8908, Level 22, State 6, Line 1 Table error: Database ID 23, object ID 901578250, index ID 0. Chain linkage mismatch. (1:753306)->next = (1:753307), but (1:753307)->prev = (1:706408).
It seems its consistency error that Checkdb was not able to repair. Should I run checkdb again with All_ErrorMSGS ? to know whts going on ? OR any other way to cope with this error ? Indexid=0 seems cluster index issue..
As I asked earlier...
Now, please run this so I can see if there are any remaining errors DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
jitendra.padhiyar (1/15/2013) Just googled error message and found this issue occurs because the SHRINK operation cannot remove a page from the SYSFILES1 system table on the primary data file of the database. And we can fix it by applying latest service pack of SQL Server 2000!!
Err, no it is not caused by shrink trying to remove a page from sysfiles1 and no you cannot fix it by applying a service pack.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|
|
SSC-Dedicated
           
Group: General Forum Members
Last Login: Today @ 12:59 PM
Points: 37,640,
Visits: 29,895
|
|
Jayanth_Kurup (1/15/2013) @Gail , would it make sense now to add a clustered index or rebuild the clustered index ?
No, it will fail.
Are you able to access the table , can you create a copy of the table ?
No, it will fail.
Gail Shaw Microsoft Certified Master: SQL Server 2008, MVP SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter We stand on the bridge and no one may pass
|
|
|
|