I am getting this allocation error on sql 7.0 which won't go away with checkdb (repair_allow_data_loss). I had a suspicion about one table. After dropping this particular table CHECKDB(repair) removed all the allocation errors. The application people are dead against dropping the table. I was wondering if there is any way around this problem short of restoring. I have already tried dbreindex. Checktable does not return any error on this table. This table holds all the transaction logs for the application.
Server: Msg 8906, Level 16, State 1, Line 0
Page (1:656) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 100_PCT_FULL'.
thx,
BXWhy not transfer the data to another table (DTS, BCP, EIEIO), drop the bad table, repair the database, then recreate the table and transfer the data back? Off hours, of course.
Richard
Originally posted by bxmakin
I am getting this allocation error on sql 7.0 which won't go away with checkdb (repair_allow_data_loss). I had a suspicion about one table. After dropping this particular table CHECKDB(repair) removed all the allocation errors. The application people are dead against dropping the table. I was wondering if there is any way around this problem short of restoring. I have already tried dbreindex. Checktable does not return any error on this table. This table holds all the transaction logs for the application.
Server: Msg 8906, Level 16, State 1, Line 0
Page (1:656) in database ID 7 is allocated in the SGAM (1:3) and PFS (1:1), but was not allocated in any IAM. PFS flags 'MIXED_EXT ALLOCATED 100_PCT_FULL'.
thx,
BX
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment