Repair Suspected Database

Repairing Suspect SQL Database

I'm not a DBA but I have a real life experience repairing a suspect databases twice. I guess I can say that I was unlucky at that time as I was presented in a tough situation where I was still in the process of learning how things work and we didn't have a DBA resource (remember I am a developer), but still consider it lucky as even some experienced DBAs might not have even experienced this situation. I experienced a similar situation before, and restoring it was easy before as we have, but that was easier as I have the proper restore points.

Now in this situation, the backups had failed so the last clean backup we had was 2 weeks old, so I could only rely on that one plus the current transaction log which is not backed up for now. So the first thing that came to my mind was to backup the transaction log so I could easily restore the full lot. I tried to backup the transaction log, but I had to remove the suspect status first by running this TSQL:

Collapse | Copy Code

sp_resetstatus 

Now it was not a suspect anymore, I was hoping to run the backup of transaction log by using this TSQL:

Collapse | Copy Code

UPDATE-3 POSTMAN NAME CHANGE ERROR

After update  Meghdoot7.0 with  Update 3 if you modify  Postman name in Supervisor. The postman name appears twice while taking returns (Old Postman Name+New Postman Name). Because of this bug day end cannot be done. Now CEPT MYsore has Provided two exl to solve this issue, One Exe and Two dll to solve this issue.

DOWNLOAD

PLI RELATED PROBLEM IN ACCOUNTS MODULE

CLICK HERE TO DOWNLOAD PATCH