From: masri999 on 26 Oct 2006 20:01 When I executed DBCC Memory Status following are the out put Buffer Distribution Stolen 187191 Free 1026 Procedures 6698 Inram 0 Dirty 154661 Kept 0 I/O 0 Latched 772 Other 436084 Buffer Counts Committed 786432 Target 786432 Hashed 591517 Internal Reservation 510 External Reservation 2291 Min Free 1024 Visible 200408 Procedure Cache Total Procs 563 TotalPages 6698 InUsePages 6576 Dynamic Memory Manager Stolen 192631 OS Reserved 920 OS Committed 898 OS In Use 894 General 5017 Query Paln 183216 Optimizer 0 Utilites 658 Connection 4110 Global Memory Objects Resource 3428 Locks 477 SQLCache 850 Replication 2 LockBytes 2 ServerGlobal 22 Xact 260 Query Memory Manager 6 Grants 6 Waiting 0 Maximum 5922 Available 2389 Now I am getting the following error 2006-10-23 14:34:20.91 spid904 BPool::Map: no remappable address found. 2006-10-23 14:34:20.94 spid465 BPool::Map: no remappable address found. 2006-10-23 14:34:20.94 spid62 AWE mapping status: 2006-10-23 14:34:20.94 spid62 There are 200408 pages in the AWE window 2006-10-23 14:34:20.94 spid62 193325 pages have a bstat of 000000 2006-10-23 14:34:20.94 spid62 3043 pages have a bstat of 00000b 2006-10-23 14:34:20.94 spid62 2844 pages have a bstat of 000009 2006-10-23 14:34:20.94 spid62 633 pages have a bstat of 000020 2006-10-23 14:34:20.94 spid62 563 pages have a bstat of 001001 2006-10-23 14:34:20.94 spid62 BPool::Map: no remappable address found. 2006-10-23 14:34:20.96 spid530 BPool::Map: no remappable address found. 2006-10-23 14:34:20.97 spid240 BPool::Map: no remappable address found. 2006-10-23 14:34:20.99 spid275 BPool::Map: no remappable address found. 2006-10-23 14:34:21.02 spid465 BPool::Map: no remappable address found. System is configured with AWE and 6.5 GB to SQL Server. Total Mem: 8 GB Questions 1. I see QueryPlan very high . What is the difference between QueryPlan and Procedures Counter . My experiment indicates QueryPlan Value is always greater than Procedures . Is it correct ? Can Some one explain query plan correctly . It is confusing from the MS Article 2. I suspect QueryPlan counter is high ? Is the problem is in BufferPool or MemtoLeave ? 3. Statements executed mostly are prepared statements
|
Pages: 1 Prev: Snap-in creation failed Next: Converting a varchar to int |