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
- String Replace in text file with Powershell
- Forgotten sa password
- Sql server installation is either corrupt or has been tampered with error getting instance id from name
- Find Weak passwords in SQL Server
- Event ID 55 : The file system structure on the disk is corrupt and unusable on volume
- Career in DBA
- Error 3254 – The volume on device BACKUP_PATH is empty
- SQL auto close - Keep it turned off
- Windows Pagefile size for dedicated SQL Servers
- SQL Database Corruption
17 May,2012 by Jack Vamvas
Question: This SQL Server Error message appears in the logs :
“Timeout occurred while waiting for latch: class 'LOG_MANAGER', id 000000001B8009F8, type 4, Task 0x0000000004ED9288 : 0, waittime 300, flags 0x1a, owning task 0x0000000B671882C8. Continuing to wait.”
How do I fix?
Answer:
1. Check for disk bottlenecks through Windows Perfmon during maintenance processing. Read Window Perfmon scripting, SQL Server perfmon and how to perfmon
2. Don't run heavy processing jobs in parallel with backup and db reindexing
3. Check your service packs are up to date..
4. Check the Auto-Grow on Log files is set to Fixed growth, rather than percentage. On large transaction , if you set it at 10% , a large file such as 30GB – will request 3 GB growth. Whereas , if you set it a .5 GB . Read SQL LOG FILE AUTOGROW performance troubleshooting
Related Posts
How to report a SQL Server performance problem
SQL Server Performance Killers
SQL Server – Find queries causing Lock Timeouts per second -
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: |