Dear experts,
After running the DBCC checkdb against master databas with DATA_PURITY argument, we recieved the error 2570 in sys.sysbinobjs. The complete output is the below (it's in spanish but you'll get it):
Command: DBCC CHECKDB ([master]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY
Mensaje 2570, Nivel 16, Estado 2, Servidor CRM-S, L¡nea 1P gina (1:354), zona 28 en el id. de objeto 58, id. de ¡ndice 1, id. de partici¢n 281474980511744, id. de unidad de asignaci¢n 281474980511744 (tipo "In-row data"). El valor de la columna "name" est fuera del intervalo del tipo de datos "nvarchar". Actualice la columna de forma que contenga un valor v lido.CHECKDB detect¢ 0 errores de asignaci¢n y 1 errores de coherencia en la tabla 'sys.sysbinobjs'. (id. de objeto 58).CHECKDB detect¢ 0 errores de asignaci¢n y 1 errores de coherencia en la base de datos 'master'.
Then, I followed the instructions in this KB article and checked the data with a DAC connection. The real problem is that the suggested solution is to update the row with a valid value, but the object is a system catalog. Unfortunately, we discovered the problem too late and our master db backups were already corrupts.
I don't think this is a crucial problem for our system, we don't even use Service Broker, but of course I'd like to have it fixed. The current SQL version is 10.50.2550 (SQL 2008 R2 SP1 with Microsoft Security Bulletin MS12-070). Maybe applying SP2 will fix the problem but I really don't feel comfortable running a patch upgrade with problems in master db.
Any help will be really appreciated.
Cheers,
Javier.