Hi all
The sql error logs are reporting data integrity errors on one of our databases. As a sql admin newbie, I'm wondering what the best way to approach this issue is. I've restored the db to a test server so i can try a few different things - the first thing i tried to do is run a dbcc checkdb on the database - this is the error i'm getting:
--
Server: Msg 8968, Level 16, State 10, Line 1
Table error: IAM page (1:110) (object ID 2, index ID 255) is out of the range of this database.
Cannot shrink log file 2 (EVLonstore01_Log) because all logical log files are in use.
--
The database also appears to have a load of free white space but running dbcc shrinkdb also failed...
Note that during our maintenance plans, we do not check the "automatically allows sql to fix errors' option in the Integrity section, as the db needs to be in single-user mode to do so and we don't have a maintenance window on this particular db to allow us to do this.
I think the next thing im going to try is setting it to single-user mode on the test server and running the integrity checks with the repair option switched on.. but it would be interesting to know the innards of what's causing the problem and how to fix it manually...
Any tips??????
Div
The sql error logs are reporting data integrity errors on one of our databases. As a sql admin newbie, I'm wondering what the best way to approach this issue is. I've restored the db to a test server so i can try a few different things - the first thing i tried to do is run a dbcc checkdb on the database - this is the error i'm getting:
--
Server: Msg 8968, Level 16, State 10, Line 1
Table error: IAM page (1:110) (object ID 2, index ID 255) is out of the range of this database.
Cannot shrink log file 2 (EVLonstore01_Log) because all logical log files are in use.
--
The database also appears to have a load of free white space but running dbcc shrinkdb also failed...
Note that during our maintenance plans, we do not check the "automatically allows sql to fix errors' option in the Integrity section, as the db needs to be in single-user mode to do so and we don't have a maintenance window on this particular db to allow us to do this.
I think the next thing im going to try is setting it to single-user mode on the test server and running the integrity checks with the repair option switched on.. but it would be interesting to know the innards of what's causing the problem and how to fix it manually...
Any tips??????
Div