Fastest way to fix MSSQL Database with Suspect mode

I had a situation where multiple databases (50+ Databases) changed to Suspect mode.
Simple solution: (assume the DBs are in Server-A, Availability group and Server-B is configured as secondary server)
* Fail over the availability group to Server-B
* Resume Data Movement in Server-A
* Fail back the availability group to Server-A

Other references to fix the problem:

Note: Used Object Explorer Details (F7) option to resume data movement on multiple databases:

This entry was posted in SQL, SQL Error, SQL Server, Uncategorized and tagged , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s