Search
Subscribe
Categories
- Backup and Restore
- Capacity Planning
- Compression
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- DBCC
- Deadlocks
- Default Trace
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Execution Plan
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Isolation levels
- Jobs
- Latches
- Links
- Locking
- Memory
- Monitor Performance
- MS DTC
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Blocking
- SQL Cachestore
- SQL DAC
- SQL Default Trace
- SQL DTS
- SQL Error Logs
- SQL Execution Plan
- SQL Optimizer
- SQL problems
- SQL Query Tuning
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL Trigger
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- Stored Procedure
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- View
- Virtualization
- Wait Stats
SQLServer-DBA.com Links
Recent Posts
- The value of training and How to convince your boss
- SQL Error 1204 - cannot obtain a LOCK resource at this time
- Multi-statement table valued function and inefficient Excecution Plan
- SQL Server Export to Excel with Powershell
- Who dropped the table in SQL Server
- List sql database roles
- SQL Execution Plan - Comparing Estimated Rows and Actual Rows
- DCOM got error "Logon failure: unknown user name or bad password” Event 1004
- SQL Server Triggers and Performance
- SQLServerAgent could not be started (reason: Error creating a new session)
03 July,2012 by Jack Vamvas
Question: We had a hardware failure which caused the server supporting the ESX host to crash. The administrator issued a VMotion onto another server in the Cluster. Upon restart the SQL server is recovering very slowly. What can be causing this delay?
Answer: A variety of reasons cans cause a slow recovery on a SQL Server restart after a hardware failure or power outage , possibilities include
a) CHECKPOINT hadn’t run after a large amount of transactions. This leaves SQL dirty pages
b) SQL Server had a large amount of active transactions when the server crashed
c) SQL Server shutdown was not clean. Hardware failure\ power outage are typical reasons.
d) The sp_confgure option “recovery interval” is not at the default setting (default = 0) . Basically , recovery_interval manages the checkpoint frequency.
Follow these steps - Server sudden shutdown unavailable
Author: Jack Vamvas (http://www.sqlserver-dba.com)
Verify your Comment
Previewing your Comment
This is only a preview. Your comment has not yet been posted.
As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.
Having trouble reading this image? View an alternate.
Posted by: |