Question : MSSQL$MICROSOFT##SSEE Event 824

Having issues with a program called Act. Kicking users out and keeping up to 4 people out at a time. We have Act premium ex 2008. Everything has been working fine for about 1 year. Latest change only is we now have about 3000 clients. Most Pc's only have about 1gb of ram and all have windows xp pro; many only with sp2.

The following error has been showing up about 30 or more times today alone.

Error is showin in event viewer on server: MSSQL$MICROSOFT##SSEE Event 824 : BODY OF ERROR MSG

SQL Server detected a logical consistency-based I/O error: torn page (expected signature: 0x55555555; actual signature: 0x400415). It occurred during a read of page (1:358318) in database ID 5 at offset 0x000000aef5c000 in file 'c:\WsusDatabase\SUSDB.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

I Do not know how to perform a DBCC CHECKDB.

I also need some input as to what may be causing the error. Will adding memory to PCs help and or what else we need.

Also in Act almost every day I perform a database maintenance check and repair.

Answer : MSSQL$MICROSOFT##SSEE Event 824

This means the database has been damaged. A "Torn Page" is low-level physical database corruption

If possible, stop the SQL (ACT7) service and make a copy of the ADF and AFL files before continuing.

The recommended recourse (if the database is attached is to run a  Repair Database) in ActDiag - this may or may not resolve the problem.
http://kb.sagesoftwareonline.com/cgi-bin/sagesoftwareonline.cfg/php/enduser/std_adp.php?p_faqid=19642

If  not, then go to a backup if you have one.

If there is no backup and you must have the data,  you'll need to open an incident with Microsoft - they may or may not be able  to go in and manually recover the data and create a new database for you If not, contact Sage Database repair and they should be able to help repair it
http://www.act.com/support/databaseservices/databaserepair/

For future reference, you might add the ACT zone to questions on ACT! - http://www.experts-exchange.com/Database/Contact_Management/ACT/