i am seeing a recurrence of SPIDs that are blocking themselves with lastwaittypes of pagelatch. I am concerned about the buffer pool needing more memory as it currently has the 2gb native x86 on it and contains databases that are up to 26 GB.
SPIDs blocking one another with PAGELATCH_EX last wait types
Hot Topic
- Printing large reports in single page.
- Remote connection to SQLEXPRESS doesn't work!
- Edit Xml data in ntext Field
- ANSI SQL-99 Compliance Level
- SQLExpress Problems
- Problems with installing SQL Server 2005 Developer Edition
- Creating New DB using SMO
- Using Teradata .NET data provider as data source
- Localized subject line
- SQL Update statement
SQL Server
- SNAPSHOT Replciation - Last distributed transaction LSN ?
- How to mimic replmerg.exe in vb.net
- Index on bit fields in SQL Server Management Studio
- cannot login
- Execute SSIS package from ".vbs" file
- SQL Management Studio Express
- SQLPrepare and SQLExecute returns Permission Denied in SQL 2005
- Convert int to ntext
- equivalent of render command and session header in reporting services 2005
- problems to conect a cube in client due to panda antivirus
SPIDs blocking one another with PAGELATCH_EX last wait types
Kimmy
The latch waits aren't really an indication of memory limitations. Starting with SQL 2000 sp4 the waittype column is populated when the spid is waiting on latches. It is possible, and normal, for the situation you describe to appear. See this article for some more information: http://support.microsoft.com/kb/906344/en-us