This article will guide you on methods to resolve SQL error 825 which indicates a major disk problem and not a SQL server problem.
The connection to #SQL server cannot be established or is no longer usable. There can be various causes of this #error. The most common causes are that Microsoft Dynamics NAV Server has stopped or the connection to SQL #Server is not configured correctly.
To find SQL errors:
i. In SQL Server Management Studio, select Object Explorer.
ii. In Object Explorer, connect to an instance of SQL Server, and then expand that instance.
iii. Find and expand the Management section (assuming you have permissions to see it).
iv. Right-click SQL Server Logs, select View, and then choose SQL Server Log.
Every SQL Server #database has a transaction log that records all transactions and the database modifications made by each transaction. The transaction log is a critical component of the database. If there is a system failure, you will need that log to bring your database back to a consistent state.
To get SQL query history in SQL Server:
1. In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
2. Expand SQL Server Agent, and then expand Jobs.
3. Right-click a job, and then click View History.
4. In the Log File Viewer, view the job history.
5. To update the job history, click Refresh.