SQL Server Performance Forum – Threads Archive
warning about latchHi I am getting these error, contineously and they stop after sometime. WARNING: EC 5e8a03c0, 0 waited 300 sec. on latch 8264bcb0. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x227515D0.
WARNING: EC 388e15d0, 0 waited 300 sec. on latch 8264bcb0. Not a BUF latch.
Waiting for type 0x4, current count 0xa, current owning EC 0x227515D0. I want to know what is this all about and i would like to know how to go about resolving this issue.
SQL BOL Says: – Latching
Latches are very lightweight, short-term synchronization objects protecting actions that need not be locked for the life of a transaction. They are primarily used to protect a row when read for a connection. When the relational engine is processing a query, each time a row is needed from a base table or index, the relational engine uses the OLE DB API to request that the storage engine return the row. While the storage engine is actively transferring the row to the relational engine, the storage engine must ensure that no other task modifies either the contents of the row or certain page structures such as the page offset table entry locating the row being read. The storage engine does this by acquiring a latch, transferring the row in memory to the relational engine, and then releasing the latch.
Avoid running database backup/ reindex or heavy IO operational queries all together.
http://www.sqlnewsgroups.net/group/microsoft.public.sqlserver.server/topic203.aspx If Full-Text service is running on server, then pls go to below link: –
Deepak Kumar –An eye for an eye and everyone shall be blind
check this links for further reading