1. Identify the table in which the Index or Headers have been corrupted. In this example, we're using the “Adjustments Database” table.

2. Open DBRebuild and attempt to rebuild the table.

If DBRebuild Cannot Fix the Corruption:

1. Assign an alias to a temporary location for the data to be copied. In this example, We've named it 'TempData,' and we've created it in the file path “C:\Program Files(x86)\Cyrious\SMS\”

2. Run the following SQL query in the query tool. Note that the filepath to the data is subject to change. Remember that the filepath leading to TempData in the first line is only an example.

Insert into “C:\Program Files(x86)\Cyrious\SMS\TempData\Adjustments Database”

Select * from “Adjustments Database”

3. Re-integrate the data in the temporary table (TempData\Adjustments Database) by copying the corrected table files into place over the corrupted ones.

If neither DBRebuild or the SQL Query will work on their server, you may need to copy the data to your machine, work on it locally, then transfer it back after it has been corrected.

1. Browse to the folder in which their data is stored (default is \SMS\Data ). Copy all of the files that share the same name as the table that is corrupted into a separate folder and compress them. Transfer the compressed data back to your machine.

2. Decompress the data and attempt to fix in DBRebuild and/or DBBrowser using the instructions at the top of this article.

3. Once the data is recovered, compress it and transfer it back to the customer's server for re-integration into their live data.

4. Re-integrate the data in the temporary folder with the live data by copying the corrected table files in the temporary folder into place over the corrupted ones in the live data folder.