Ghotekar Rahul
Ghotekar Rahul

Reputation: 342

SQL server Warning: Fatal error 829 occurred at Oct 10 2019 12:48 PM. Note the error and time, and contact your system administrator

The 2 table not insert or select or delete or drop table command execute then show error below:

The error I'm receiving

Warning: Fatal error 829 occurred at Oct 10 2019 12:48PM. Note the error and time, and contact your system administrator.

DROP TABLE [dbo].[tbl_SalesMaster_tmp]
GO

Upvotes: 0

Views: 2212

Answers (1)

cdrrr
cdrrr

Reputation: 1112

Just a quick search on Google and find a similar thread here. However, I extracted the possible solution for an easy reference.

Means there's an I/O subsystem problem. Is something called a 'hard I/O error'. SQL Server asks the OS to read a page and it says no - this means the I/O subsystem couldn't read the page in question.

The CHECKDB output means that it couldn't create the internal database snapshot that it uses to get a transactionally-consistent point-in-time view of the database. There are a number of different causes of this:

There may not be any free space on the volume(s) storing the data files for the database The SQL service account might not have create-file permissions in the directory containing the data files for the database If neither of these are the case, you can create your own database snapshot and run DBCC CHECKDB on that. One you have, run the following:

DBCC CHECKDB (yourdbname) WITH NO_INFOMSGS, ALL_ERRORMSGS

Whatever the results are, you're looking at either restoring from a backup, extracting data to a new database, or running repair. Each involves varying amounts of downtime and data-loss. You're also going to have to do some root-cause analysis to figure out what happened to cause the corruption in the first place.

By the way - do you have page checksums enabled? Have you looked in the SQL error log or Windows application event log for any signs of corruption or things going wrong with the I/O subsystem?

Upvotes: 1

Related Questions