St. Robert, MO, USA Police Department Repairs Large MS SQL Database by using Stellar Toolkit for MS SQL

St. Robert Police Department is the law enforcement authority in St. Robert- Missouri, which is responsible for improving the quality of life by providing a safe and secure environment in the city.

St. Robert Police Department had been using a sophisticated SQL Server database to serve various needs such as providing police performance data to Home office, record keeping, reports booking, accessing reports, and data lifecycle management.

Approx. 30 people in the police department had been using this SQL database, with major dependencies on the system to perform their duties on a daily basis. Of late, some users had reported that they were unable to fetch any information using web-based interface of the SQL Server reporting system; the problem had surfaced without any prior symptoms or precedence.

The system administrator diagnosed database corruption as the cause of this problem; initial investigation revealed that the web app was unable to connect with the backend database, which was most likely due to corruption. Apparently, the database had turned into Suspect Mode due a sudden power outage while the data center backup system also malfunctioned.

Root Cause Analysis
The administrator checked the SQL error log on suspect_pages to find that transactional log file of the database had turned corrupt which is a common issue associated with erratic power supply. Error code 823 that indicates a suspect page was listed down in the event_type for multiple pages; a significant number of pages in the database had been marked suspected as being bad.

Recovery Attempts
The system administrator sought to resolve this issue at multiple levels starting with recovery from backup, considering it’s the least risky in terms of potential data loss.He was relying on SnapManager® – NetApp’s integrated data management system for SQL – for backup; however, it turned out that the tool wasn’t configured on the server in the first place, which came as a rude surprise.

Next, he attempted recovery from a ‘QA’ instance of the database by using T-SQL. Successful recovery with this method is possible only if the version and build for both production and test databases match, which unfortunately wasn’t the case here. So, database recovery again failed due to a mismatch in the server versions.

As last resort, the administrator decided to use Emergency state for dealing with the database in Suspect Mode. Emergency state would allow direct access to the Suspect database and its configuration settings. It would also allow exporting the database and running DBCC CHECKDB commands to resolve corruption.

Client

Police Department, St. Robert, Missouri

Business Needs

Repair corrupt MS SQL database and
reinstate database access

Solution

Stellar Toolkit for MS SQL

Benefits

– Full database recovery in less than 24 hours

– Restoration of database with 100% integrity

– Minimal human efforts & time

– Futureproof solution for SQL database
corruption

Success Stories

Key Technologies

Get in Touch Say Hello