DBCC CHECKDB on REPLICATED DB's

[btturner]

I am relatively new to SQL 2K Replication (1 way transactional in this case). Receiving Integrity Check errors on 2 (of 5) source/publisher DB's. These 2 DB's are the only 2 (of 5) DB's w/ Replication activated on my SQL Server. (fyi, my distributor is on the same server as these 2 DB's)

Has anyone encountered a similar issue? If so, any suggestions for resolution?

Should I place the DB into single user mode and run DBCC CHECKDB w/ REPAIR option? (how would this affect target replicated data)

thx for any assistance / suggestions...

ERROR Msgs received in Event Viewer

8957: DBCC CHECKDB (CustomerDB) executed by ABCINT\ABC found 5 errors and repaired 0 errors.

SQL Server Scheduled Job 'Check_Integrity_CustomerDB' (0x8D3A53095FBF6A4EA921163A687EFBF7) - Status: Failed - Invoked on: 2004-12-26 20:05:07 - Message: The job failed. The Job was invoked by Schedule 820 (Check_Integrity_CustomerDB). The last step to run was step 1 (Check_Integrity_CustomerDB).

 

[mrdenny]

You should repair this errors as sone as possible. You will need to stop the replication agents before you run checkdb with repair.

Besure to do a full backup before hand, just in case.

As long as you don't have to use the repair_allow_data_loss flag it shouldn't effect replication at all, other than the fact that you have to shut down the replication while you repair the database.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)

 

[btturner]

Denny - right on! I cancelled the Snapshot agent prior to placing the DB in single user mode.. then had to run CheckDB w/ repair_allow_data_loss. It resolved my integrity check - when I restarted up the Snapshot agent (job) it replicated the article (only 1 in this case) onto my target server.

Thx-

 

[mrdenny]

Excelent. Glad it worked.

Denny

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

(My very old site)