Webtrends Analytics 9.2x and 8.7d use MS SQL Server Express 2008 by default:
Note: Installation of Management Studio Express 2008 requires installation of the Microsoft Web Platform first, after which Management Studio Express 2008 will follow.
2. After installation, open the application from Start > Programs > Microsoft SQL Server 2005/2008 > SQL Server Management Studio Express.
3. Log into the database using Windows Authentication
4. Expand Databases, then right-click on wt_sched and choose "Properties."
5. Select "Options" and scroll to the bottom in the pane on the right.
6. Change "Restrict Access" to "SINGLE_USER."
7. Select OK and repeat the above steps for the wtMaster section of the database.
8. Select "New Query" from the toolbar, and in the query pane that opens, paste in the following commands:
dbcc checkdb('wtMaster',REPAIR_REBUILD) dbcc checkdb('wt_sched',REPAIR_REBUILD) 9. Select the "Execute" button to repair the database. 10. Perform the steps outlined in 4-6 above and change the databases back to "MULTI_USER" from "SINGLE_USER."
Note: Changing the database back to MULTI_USER mode may require logging out and logging back in using SQL Server Management Studio Express in order to change both parts back to their original settings. Attempting to make these changes may result in an error saying there are too many connections. Closing Management Studio and then re-opening it again will allow these changes to take effect.
Additionally, while the 'scan' (no parameters passed) can be run while in the standard multi-user mode, performing repairs requires changing the database to single-user mode.
DBCC CHECKTABLE ('table_name') - In order to check an entire database in Microsoft SQL Server the following command will need to be used via command line or query manager.
DBCC CHECKDB ('database_name') - Both commands have the following repair options:
REPAIR_ALLOW_DATA_LOSS - Performs all repairs done by REPAIR_REBUILD and includes allocation and deallocation of rows and pages for correcting allocation errors, structural row or page errors, and deletion of corrupted text objects. These repairs can result in some data loss. The repair may be done under a user transaction to allow the user to roll back the changes made. If repairs are rolled back, the database will still contain errors and should be restored from a backup. If a repair for an error has been skipped due to the provided repair level, any repairs that depend on the repair are also skipped. After repairs are completed, back up the database.
REPAIR_FAST - Performs minor, non-time-consuming repair actions such as repairing extra keys in non-clustered indexes. These repairs can be done quickly and without risk of data loss. For a complete list of syntax and examples for checking tables and databases refer to the following Microsoft Knowledge Base articles:
For a complete list of syntax and examples for checking tables and databases refer to the following Microsoft Knowledge Base articles: