Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
NBI
Starting Member
1 Post |
 Posted - 2008-04-11 : 13:35:14
|
| Today my company was running our servers and we got this error message:cannot display subcampaign. database error:[microsoft][odbc sql server driver][sql server]Warning :fatal error 823 occurred at apr 11 2008 1:20pmnote: time reset itself when we turn comp on..First off we run a telemarketing company that does phone sales.this error is stopping us from inputing new calling list to the computer. The program we use is Chase data power server. We cannot run a backup because we called through a list of numbers today and if we use the restore it will call all the Do not calls back from the old list. Is there anyway to solve this with out using a restore or backup feature? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-04-11 : 16:23:39
|
| This forum is used for data corruption found by running DBCC CHECKDB. Does that command return errors?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
|
|
SwePeso
Patron Saint of Lost Yaks
30421 Posts |
Posted - 2008-04-11 : 16:33:57
|
quote:
Books Online
Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG of %S_BUF.Explanation Microsoft SQL Server encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. The parameters in the error message refer to internal structures and don't often help determine which device is involved. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved. Action Check the accessibility and condition of the device in question. After you have identified and corrected the problem, execute DBCC CHECKDB to ensure that no other damage was caused by the bad device. For information about using DBCC CHECKDB, see "DBCC CHECKDB" in Microsoft SQL Server Transact-SQL and Utilities Reference. Important If executing DBCC CHECKDB with one of the repair clauses does not correct the index problem or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider. In addition, run hardware diagnostics and correct any problems.
Also see Microsoft Knowledgebase article http://support.microsoft.com/kb/274310/EN-US/
E 12°55'05.25"N 56°04'39.16" |
|
|
|
|
|
|
Error 823