Search
Subscribe
Categories
- Backup and Restore
- Configure
- Contact me
- CPU
- Data Architecture
- Data Import and Export
- Database Mirroring
- DBA
- DBA Scripts
- Deadlocks
- Development
- Disaster Recovery
- Disk Storage
- DMV
- Documentation
- Event Log
- Function
- High Availability
- Indexes
- Install & Setup
- Interviews
- IO Subsystem
- Jobs
- Links
- Locking
- Memory
- Monitor Performance
- MSDB
- Network
- Object Management
- Pagination
- Partitioning
- Performance
- Powershell
- Security Management
- SQL Agent
- SQL Azure
- SQL Cachestore
- SQL Error Logs
- SQL Optimizer
- SQL problems
- SQL Server Error Tips
- SQL Server Management Studio
- SQL Server Profiler
- SQL Server Tuning
- SQL View
- SQLServer-DBA News
- SSIS
- Statistics
- T-SQL
- TempDB
- Tools
- TPC-H
- Transaction Logs
- Virtualization
- Wait Stats
Recent Posts
- How to check Operating System type with Powershell
- ALTER TRACE and developers
- Predict ALTER INDEX REORGANIZE finish time
- Cannot connect to SQL Server
- Timeout occurred while waiting for latch: class 'LOG_MANAGER'
- The instance of the SQL Server Database Engine cannot obtain a LOCK resource at this time
- How to create a SQL Server Security Audit
- Cannot use Large Page Extensions: lock memory privilege was not granted
- Compare two files with Powershell
- Export-CSV Powershell
SQL Server Books online defines Async_io_completion as “Occurs when a task is waiting for I/Os to finish “
Mainly a symptom of an IO bottleneck. Cross check by identifying other wait stat indicators such as :IO_COMPLETION ,WRITELOG,PAGEIOLATCH_X. The appearance of at least one of these along with ASYNC_IO_COMPLETION – near the top of the wait stats indicates a serious IO bottleneck
Any SQL Server task waits for IO completion – this is completely normal part of SQL Server processing. But when the wait for IO completion is slow there is a problem
A few issues to consider and approached to minimizing Async_io_completion.
1)Maintain Random access \ Sequential access files on different drives .
2)Are you experiencing IO delay messages in the error logs. This is a strong indicator , as it reports on IO delays – outside of the SQL Server process space.
the article : IO Requests taking longer than 15 seconds to complete gives an in depth explanation
3)Analyse the SQL Server Performance Stack
CPU Cores
Windows
SQL Server
Cache
FC HBA
Fibre Channel Switch
Storage Controller
Storage Controller Cache
Disk
LUN
Source:Jack Vamvas (http://www.sqlserver-dba.com)
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: |