SQL 2012 Memory usage analysis

We have this clustered SQL Server, win 2008 R2 + SQL 2012 Standard SP2,
Server RAM is 64GB, maximum memory is set at 50GB, and minimum memory is set at 10GB.
When I check memory usage, it seems
CLR takes more memory than Buffer Pool, is it normal? Or does it show memory allocation issue? Thanks a lot!
The "total server memory" and "target server memory" performance counters are both 50GB.
Please kindly see below screen shots below:

Hi Vivian,
I would assume you are asking question related to SQL Server 2012 memory the whole discussion would change if it is SQL Server 2008 r2 memory
You are not drawing correct information from first query.
CLR has Reserved 6 G but ONLY committed 12 MB. And that too you are looking at virtual memory which is 6TB for SQL Server process so of course CLR can reserve there is actually no issue with it. A committed memory is actually what SQL Server is using
reserved in simple language is what SQL Server thinks it might need in near future.
As you said Target and total memory are same its good.
For both 2012 and 2008 r2 below query will give total memory utilization by SQL Server instance
select
(physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
(locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
(total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
process_physical_memory_low,
process_virtual_memory_low
from sys. dm_os_process_memory
If you want to see Breakdown of memory utilized by various clerks in 2008 r2
select
type,
(SUM(single_pages_kb)/1024) Single_page_allocator_memory,
(SUM(multi_pages_kb)/1024) multi_page_allocator_memory,
(sum(awe_allocated_kb)/1024) [AWE API memory]
from sys.dm_os_memory_clerks
group by type
order by Single_page_allocator_memory desc
For 2012
select type,
(SUM(pages_kb)/1024) as Memory_Utilized
(sum(awe_allocated_kb)/1024) as Memory Allocated by AWE API
from
sys.dm_os_memory_clerks
group by type
order by Memory_Utilized desc
Starting from 2012 Max server memory controls much more than buffer pool
Max server memory controls SQL Server memory allocation, including the buffer pool, compile memory, all caches, qe memory grants, lock manager memory, and CLR memory (basically any “clerk” as found in dm_os_memory_clerks). Memory for thread stacks, heaps,
linked server providers other than SQL Server, or any memory allocated by a “non SQL Server” DLL is not controlled by max server memory
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Similar Messages

  • SQL 2012 Memory Usage

    Hi,
    We have a core sql database  server, which have 256 GB physical memory ,and give maximum physical memory to sql server 240000 MB, sql server service startup account  has locked memory privilege.
    We found that the free memory is 12094108 KB,but the Page Life Expectancy counter is low,about 300.
    Does anybody give some advice why sql server don't (or can't) use free memory, and how to find which parts inside sql server took up these free memory?
    Many thanks.
    SQL Server Version:
    Microsoft SQL Server 2012 - 11.0.5532.0 (X64) 
    Jul 14 2014 15:00:27 
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    And this is a clustered sql instance and as a primary node of ag.
    Attachments are some dmv results.

    logdate processinfo
    text
    2014/9/12 3:10 AM Server
    Microsoft SQL Server 2012 - 11.0.5532.0 (X64) 
    Jul 14 2014 15:00:27
    Copyright (c) Microsoft Corporation
    Enterprise Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    2014/9/12 3:10 AM Server
    (c) Microsoft Corporation.
    2014/9/12 3:10 AM Server
    All rights reserved.
    2014/9/12 3:10 AM Server
    Server process ID is 9692.
    2014/9/12 3:10 AM Server
    "System Manufacturer: 'HP', System Model: 'ProLiant DL980 G7'."
    2014/9/12 3:10 AM Server
    Authentication mode is MIXED.
    2014/9/12 3:10 AM Server
    Logging SQL Server messages in file 'X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\Log\ERRORLOG'.
    2014/9/12 3:10 AM Server
    The service account is 'XX\SQLAccount'. This is an informational message; no user action is required.
    2014/9/12 3:10 AM Server
    Registry startup parameters: 
    -d X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\DATA\master.mdf
    -e X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\Log\ERRORLOG
    -l X:\Sqldata\MSSQL10_50.SQLInstance\MSSQL\DATA\mastlog.ldf
    2014/9/12 3:10 AM Server
    Command Line Startup Parameters:" -s ""SQLInstance"""
    2014/9/12 3:10 AM Server
    "SQL Server detected 8 sockets with 8 cores per socket and 16 logical processors per socket, 128 total logical processors; using 128 logical processors based on SQL Server licensing. This is an informational message; no user action is required."
    2014/9/12 3:10 AM Server
    SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Detected 262133 MB of RAM. This is an informational message; no user action is required.
    2014/9/12 3:10 AM Server
    Using locked pages in the memory manager.
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    Large Page Allocated: 32MB 
    2014/9/12 3:10 AM Server
    This instance of SQL Server last reported using a process ID of 13236 at 2014/9/12 3:09:42 (local) 2014/9/11 19:09:42 (UTC). This is an informational message only; no user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 0: CPU mask: 0x000000000000ffff:0 Active CPU mask: 0x000000000000ffff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 1: CPU mask: 0x00000000ffff0000:0 Active CPU mask: 0x00000000ffff0000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 2: CPU mask: 0x000000000000ffff:1 Active CPU mask: 0x000000000000ffff:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 3: CPU mask: 0x00000000ffff0000:1 Active CPU mask: 0x00000000ffff0000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 4: CPU mask: 0x0000ffff00000000:0 Active CPU mask: 0x0000ffff00000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 5: CPU mask: 0xffff000000000000:0 Active CPU mask: 0xffff000000000000:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 6: CPU mask: 0x0000ffff00000000:1 Active CPU mask: 0x0000ffff00000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Node configuration: node 7: CPU mask: 0xffff000000000000:1 Active CPU mask: 0xffff000000000000:1. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2014/9/12 3:10 AM Server
    Lock partitioning is enabled.  This is an informational message only. No user action is required.
    2014/9/12 3:10 AM Server
    Software Usage Metrics is disabled.
    2014/9/12 3:10 AM spid21s
    Starting up database 'master'.
    2014/9/12 3:10 AM Server
    CLR version v4.0.30319 loaded.
    2014/9/12 3:10 AM spid21s
    Resource governor reconfiguration succeeded.
    2014/9/12 3:10 AM spid21s
    SQL Server Audit is starting the audits. This is an informational message. No user action is required.
    2014/9/12 3:10 AM spid21s
    SQL Server Audit has started the audits. This is an informational message. No user action is required.
    2014/9/12 3:10 AM spid21s
    "SQL Trace ID 1 was started by login ""sa""."
    2014/9/12 3:10 AM Server
    Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
    2014/9/12 3:10 AM spid21s
    Server name is 'CLSSQLInstance\SQLInstance'. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid21s
    The NETBIOS name of the local node that is running the server is 'SVRXXXXHP980'. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid27s
    A self-generated certificate was successfully loaded for encryption.
    2014/9/12 3:10 AM spid27s
    Server is listening on [X.X.X.X <ipv4> 1433].
    2014/9/12 3:10 AM spid27s
    Server is listening on [ X.X.X.X <ipv4> 1433].
    2014/9/12 3:10 AM spid27s
    Started listening on virtual network name 'ClsSQLInstance'. No user action is required.
    2014/9/12 3:10 AM spid28s
    A new instance of the full-text filter daemon host process has been successfully started.
    2014/9/12 3:10 AM spid27s
    Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
    2014/9/12 3:10 AM spid27s
    Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLInstance].
    2014/9/12 3:10 AM spid27s
    Server named pipe provider is ready to accept connection on [ \\.\pipe\$$\ClsSQlInstance\MSSQL$SQLInstance\sql\query ].
    2014/9/12 3:10 AM spid21s
    Database mirroring has been enabled on this instance of SQL Server.
    2014/9/12 3:10 AM spid32s
    AlwaysOn: The availability replica manager is starting. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid23s
    Starting up database 'mssqlsystemresource'.
    2014/9/12 3:10 AM spid33s
    Starting up database 'msdb'.
    2014/9/12 3:10 AM spid36s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid41s
    Starting up database 'CXXDB'.
    2014/9/12 3:10 AM spid38s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid42s
    Starting up database 'XXbDB'.
    2014/9/12 3:10 AM spid37s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid32s
    AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering service to start. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid39s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid32s
    AlwaysOn Availability Groups: Local Windows Server Failover Clustering service started. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid32s
    AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to start. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid32s
    AlwaysOn Availability Groups: Local Windows Server Failover Clustering node started. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid32s
    AlwaysOn Availability Groups: Waiting for local Windows Server Failover Clustering node to come online. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid32s
    AlwaysOn Availability Groups: Local Windows Server Failover Clustering node is online. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid32s
    AlwaysOn: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid23s
    The resource database build version is 11.00.5532. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid41s
    "Error: 35262, Severity: 17, State: 1."
    2014/9/12 3:10 AM spid41s
    Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID:  65538). The database will be started by the availability group. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid36s
    "Error: 35262, Severity: 17, State: 1."
    2014/9/12 3:10 AM spid36s
    Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID:  65538). The database will be started by the availability group. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid37s
    "Error: 35262, Severity: 17, State: 1."
    2014/9/12 3:10 AM spid37s
    Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID:  65538). The database will be started by the availability group. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid42s
    "Error: 35262, Severity: 17, State: 1."
    2014/9/12 3:10 AM spid42s
    Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID:  65538). The database will be started by the availability group. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid39s
    "Error: 35262, Severity: 17, State: 1."
    2014/9/12 3:10 AM spid39s
    Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID:  65538). The database will be started by the availability group. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid38s
    "Error: 35262, Severity: 17, State: 1."
    2014/9/12 3:10 AM spid38s
    Skipping the default startup of database 'XXDB' because the database belongs to an availability group (Group ID:  65538). The database will be started by the availability group. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid23s
    Starting up database 'model'.
    2014/9/12 3:10 AM Server
    Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
    2014/9/12 3:10 AM Server
    Dedicated admin connection support was established for listening remotely on port 58313.
    2014/9/12 3:10 AM spid27s
    SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014/9/12 3:10 AM Server
    SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational message. No user action is required.
    2014/9/12 3:10 AM spid32s
    AlwaysOn: The local replica of availability group 'AGGroup' is starting. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid32s
    "The state of the local availability replica in availability group 'AGGroup' has changed from 'NOT_AVAILABLE' to 'RESOLVING_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For
    more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
    2014/9/12 3:10 AM Server
    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ XXXX] for the SQL Server service. 
    2014/9/12 3:10 AM Server
    The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ xxxx ] for the SQL Server service. 
    2014/9/12 3:10 AM spid23s
    Clearing tempdb database.
    2014/9/12 3:10 AM spid23s
    Starting up database 'tempdb'.
    2014/9/12 3:10 AM spid53
    AlwaysOn: The local replica of availability group 'AGGroup' is preparing to transition to the primary role in response to a request from the Windows Server Failover Clustering (WSFC) cluster. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid53
    "The state of the local availability replica in availability group 'AGGroup' has changed from 'RESOLVING_NORMAL' to 'PRIMARY_PENDING'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error.
    For more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
    2014/9/12 3:10 AM Server
    "The state of the local availability replica in availability group 'AGGroup' has changed from 'PRIMARY_PENDING' to 'PRIMARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For
    more information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log. "
    2014/9/12 3:10 AM spid42s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid39s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid32s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid36s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid41s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid37s
    Starting up database 'XXDB'.
    2014/9/12 3:10 AM spid32s
    383 transactions rolled forward in database 'XXDB' (10:0). This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid48s
    0 transactions rolled back in database 'XXDB' (10:0). This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid39s
    CHECKDB for database 'XXDB' finished without errors on 2011-07-27 00:25:13.070 (local time). This is an informational message only; no user action is required.
    2014/9/12 3:10 AM spid49s
    Server is listening on [ X.X.X.X <ipv4> 5022].
    2014/9/12 3:10 AM spid49s
    Server is listening on [X.X.X.X <ipv4> 5022].
    2014/9/12 3:10 AM spid49s
    Started listening on virtual network name 'ClsSQlInstance'. No user action is required.
    2014/9/12 3:10 AM spid49s
    The Database Mirroring endpoint is now listening for connections.
    2014/9/12 3:10 AM spid49s
    Service Broker manager has started.
    2014/9/12 3:10 AM spid21s
    Launched startup procedure 'sp_MSrepl_startup'.
    2014/9/12 3:10 AM spid36s
    CHECKDB for database 'XXDB' finished without errors on 2011-07-27 00:25:50.283 (local time). This is an informational message only; no user action is required.
    2014/9/12 3:10 AM spid42s
    A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id  [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [C5253E8A-298A-45D8-9568-1184EC4CC3A4] has been successfully established.
     This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid41s
    A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id  [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [76DBB6D1-8A06-44DC-9357-6ACCC9AE00B7] has been successfully established.
     This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid37s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid37s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid39s
    A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id  [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [AB354017-E987-4B96-853E-6C292C9011BD] has been successfully established.
     This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid190
    Failed to verify Authenticode signature on DLL 'D:\Program Files\Microsoft SQL Server\MSSQL11.SQLInstance\MSSQL\Binn\msxmlsql.dll'.
    2014/9/12 3:10 AM spid39s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid42s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid37s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid39s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid37s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid39s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid47s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid42s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid42s
    A connection for availability group 'AGGroup' from availability replica 'CLSSQLInstance\SQLInstance' with id  [58DE3503-18BB-4C53-BD0A-705BE070EA81] to 'SVRXXXXHP580' with id [6752FE19-1AEC-4DB6-AC63-2F8A6A2E67C8] has been successfully established.
     This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid42s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid47s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid42s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid47s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid245s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid245s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid245s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid245s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid248s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid247s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid248s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid247s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid248s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid248s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid258s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid258s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid257s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid257s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid258s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid258s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid275s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid258s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid304s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid303s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid258s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid303s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid304s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid303s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid275s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {ab354017-e987-4b96-853e-6c292c9011bd}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid347s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid304s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid362s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid362s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid362s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid347s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid364s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid304s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid427
    Attempting to load library 'xpsqlbot.dll' into memory. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid427
    Using 'xpsqlbot.dll' version '2011.110.2100' to execute extended stored procedure 'xp_qv'. This is an informational message only; no user action is required.
    2014/9/12 3:10 AM spid361s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid361s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid347s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid361s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {6752fe19-1aec-4db6-ac63-2f8a6a2e67c8}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid53
    Configuration option 'Agent XPs' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014/9/12 3:10 AM spid565
    Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid565
    Using 'xpstar.dll' version '2011.110.5058' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
    2014/9/12 3:10 AM spid565
    Attempting to load library 'xplog70.dll' into memory. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid565
    Using 'xplog70.dll' version '2011.110.5058' to execute extended stored procedure 'xp_msver'. This is an informational message only; no user action is required.
    2014/9/12 3:10 AM spid361s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {c5253e8a-298a-45d8-9568-1184ec4cc3a4}. This is an informational message only. No user action is required.
    2014/9/12 3:10 AM spid605
    "SQL Trace ID 2 was started by login ""XX\SQLAccount""."
    2014/9/12 3:11 AM spid701
    "SQL Trace ID 3 was started by login ""XX\SQLAccount""."
    2014/9/12 3:11 AM spid701
    SQL Trace stopped. Trace ID = '3'. Login Name = 'XX\SQLAccount'.
    2014/9/12 3:11 AM spid360s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.
    2014/9/12 3:11 AM spid360s
    AlwaysOn Availability Groups connection with secondary database established for primary database 'XXDB' on the availability replica with Replica ID: {76dbb6d1-8a06-44dc-9357-6accc9ae00b7}. This is an informational message only. No user action is required.

  • SQL Server Memory Usage Peaks to 95% and its not releasing SQL 2012

    We are currently running SQL 2012  64 bit, Lock Pages Enabled, 128 GB. We allocated Max Memory 112000, Min Memory to 0. We have a SQL Maintenace Job which backs up (Full Backup) of our server around 11PM at that time the SQL Server memory peaks to almost
    96% even during full business hours we are constantly in the range of 56 to 60% but after 11PM within 10 minutes of the job it peaks to 95 or 96 Percentage and even after the job completes it's not releasing the memory back. I have to manually shut the sql
    service and then restart at that time it comes back to normal.
    Any suggestions/any help really appreciated.

    Here are the details Memory is at 96% I still didn't restart...Please any help appreciated...The memory detals is for 24 hours  I restarted the service around 11AM before I posted my previous message..
    Memory Used by SqLServer: 119329
    Locked Pages Used SQLServer : 105969
    Total VAS in MB : 8388607
    Process Physical Memory Low : 0
    Process Virtual Memory Low : 0
    Max Memory set to :112000
    Out of 128 Memory Last 24 hours the memory usage in %
    Percent Memory Used - Total Memory is 128.0 GB
    Last 24 Hours
    DATE / TIME
    Memory Used
    19-Dec-14
    11:46 PM
    96.24659602
    20-Dec-14
    12:46 AM
    96.24578349
    20-Dec-14
    1:46 AM
    96.25146739
    20-Dec-14
    2:46 AM
    96.24345652
    20-Dec-14
    3:46 AM
    96.27311834
    20-Dec-14
    4:46 AM
    96.28947067
    20-Dec-14
    5:46 AM
    96.18931325
    20-Dec-14
    6:46 AM
    96.09323502
    20-Dec-14
    7:46 AM
    96.07915497
    20-Dec-14
    8:46 AM
    96.07906977
    20-Dec-14
    9:46 AM
    96.0784111
    20-Dec-14
    10:46 AM
    96.07415009
    20-Dec-14
    11:46 AM
    26.03422141
    20-Dec-14
    12:46 PM
    33.57474359
    20-Dec-14
    1:46 PM
    39.466561
    20-Dec-14
    2:46 PM
    41.85940742
    20-Dec-14
    3:46 PM
    43.89071274
    20-Dec-14
    4:46 PM
    45.80877368
    20-Dec-14
    5:46 PM
    46.49493281
    20-Dec-14
    6:46 PM
    46.68486468
    20-Dec-14
    7:46 PM
    46.69701958
    20-Dec-14
    8:46 PM
    46.69994736
    20-Dec-14
    9:46 PM
    57.5012455
    20-Dec-14
    10:46 PM
    96.25695419
    I verified its a sqL job and still my memory is 95%
    It peaeked at 10:46PM and here are the details of the SQL job which started at 10:30 
    Progress: 2014-12-20 22:30:04.39 
          Source: Check Database Integrity Task      Executing query "USE [DATASTORE]  ".: 50% complete  End Progress  Progress: 2014-12-20 22:43:06.10 
          Source: Check Database Integrity Task      Executing query "DBCC CHECKDB(N'DATASTORE')  WITH NO_INFOMSGS  ".: 100% complete  End Progress
        Progress: 2014-12-20 22:43:06.11     Source: Check Database Integrity Task      Executing query "USE [ETL_Proc]  ".: 50% complete 
     End Progress  Progress: 2014-12-20 22:46:52.56     Source: Check Database Integrity Task      Executing query "DBCC CHECKDB(N'ETL_Proc') 
      WITH NO_INFOMSGS  ".: 100% complete  End Progress  Progress: 2014-12-20 22:46:52.64     Source: Back Up Database Task
            Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 20% complete  End Progress  
    Progress: 2014-12-20 22:46:52.64     Source: Back Up Database Task      Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".
    : 40% complete  End Progress  Progress: 2014-12-20 22:46:52.64   
      Source: Back Up Database Task      Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 60% complete 
       End Progress  Progress: 2014-12-20 22:46:52.64     Source: Back Up Database Task    
     Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 80% complete  End Progress  
     Progress: 2014-12-20 22:46:52.64     Source: Back Up Database Task      
     Executing query "EXECUTE master.dbo.xp_create_subdir N'P:\SQL_Backu...".: 100% complete  End Progress 
      Progress: 2014-12-20 22:46:55.63     Source: Back Up Database Task    
        Executing query "BACKUP DATABASE [ReportServer] TO  DISK = N'P:\SQL...".: 100% complete  
    End Progress  Progress: 2014-12-20 22:46:56.55     Source: Back Up Database Task    
      Executing query "BACKUP DATABASE [ReportServerTempDB] TO  DISK = N'...".: 100% complete  End Progress  Progress: 2014-12-20 22:46:57.35  
         Source: Back Up Database Task      Executing query "BACKUP DATABASE [dbamaint] TO  DISK = N'P:\SQL_Bac...".: 100% complete  End Progress 
      Progress: 2014-12-20 22:51:13.08     Source: Back Up Database Task   
         Executing query "BACKUP DATABASE [DATASTORE] TO  DISK = N'P:\SQL_Ba...".: 100% complete  End Progress
       Progress: 2014-12-20 22:51:52.72     Source: Back Up Database Task     
    Executing query "BACKUP DATABASE [ETL_Proc] TO  DISK = N'P:\SQL_Bac...".: 100% complete  End Progress  Progress: 2014-12-20 22:51:54.87 
        Source: Rebuild Index Task      Executing query "USE [ReportServer]  ".: 0% complete  End Progress  Progress:
     2014-12-20 22:51:54.88     Source: Rebuild Index Task      Executing query "ALT...  The package executed successf...  The step succeeded.

  • SQL Server Memory usage is high

    Hello,
    One of our production SQL cluster is eating up more memory on server.
    Here are the server specifications :
    OS : Windows 2008 R2 Enterprise
    SQL : SQL Server 2008 SP2 standard edition ( 2 node cluster )
    Memory : 16 GB ( 8 Gb to SQL and rest to OS )
    CPU : 8
    This server is heavily used by CLR and linked server events.
    I have seen the memory usage of databases , it's not using more than 7 GB and leaving 1 GB free in sql memory area ( from our Idera SQL dm
    monitoring tool ). I'm suspecting CLR events are causing these spikes.
    When i look at the task manager sqlserver.exe is using 15.7 Gb ( close to 16 GB )
    Not sure how to see which process are using the memory. 
    Also we are seeing the below error messages in error log very frequently
    10/27/2014 15:23:52,spid1s,Unknown,AppDomain 85 (xxxxxx) is marked for unload due to memory pressure.
    I have looked at some blogs in internet, i didnt get any correct info. I have seen this is kind of bug in SQL 2005 32-bit system but we are
    using 64 bit system.
    http://support.microsoft.com/kb/969962
    Can anyone please help me on this ?
    Thanks in advance

    Continuation of DBCC memorystatus output
    CACHESTORE_TEMPTABLES (node 0)           KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     40
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_NOTIF (node 0)                KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     16
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_VIEWDEFINITIONS (node 0)      KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     16
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_XMLDBTYPE (node 0)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_XMLDBELEMENT (node 0)         KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_XMLDBATTRIBUTE (node 0)       KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_STACKFRAMES (node 0)          KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     0
    MultiPage Allocator                      8
    (7 row(s) affected)
    CACHESTORE_STACKFRAMES (node 64)         KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     0
    MultiPage Allocator                      8
    (7 row(s) affected)
    CACHESTORE_STACKFRAMES (Total)           KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     0
    MultiPage Allocator                      16
    (7 row(s) affected)
    CACHESTORE_BROKERTBLACS (node 0)         KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     48
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_BROKERKEK (node 0)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_BROKERDSH (node 0)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_BROKERUSERCERTLOOKUP (node 0) KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_BROKERRSB (node 0)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_BROKERREADONLY (node 0)       KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     32
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_BROKERTO (node 0)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_EVENTS (node 0)               KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     16
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_CLRPROC (node 0)              KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     40
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_SYSTEMROWSET (node 0)         KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     1856
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_CONVPRI (node 0)              KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     48
    MultiPage Allocator                      0
    (7 row(s) affected)
    CACHESTORE_FULLTEXTSTOPLIST (node 0)     KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     32
    MultiPage Allocator                      0
    (7 row(s) affected)
    USERSTORE_SCHEMAMGR (node 0)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     16432
    MultiPage Allocator                      856
    (7 row(s) affected)
    USERSTORE_DBMETADATA (node 0)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     5592
    MultiPage Allocator                      0
    (7 row(s) affected)
    USERSTORE_TOKENPERM (node 0)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     3856
    MultiPage Allocator                      3960
    (7 row(s) affected)
    USERSTORE_OBJPERM (node 0)               KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     2328
    MultiPage Allocator                      0
    (7 row(s) affected)
    USERSTORE_SXC (node 0)                   KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     656
    MultiPage Allocator                      0
    (7 row(s) affected)
    USERSTORE_SXC (node 64)                  KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     8
    MultiPage Allocator                      0
    (7 row(s) affected)
    USERSTORE_SXC (Total)                    KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     664
    MultiPage Allocator                      0
    (7 row(s) affected)
    OBJECTSTORE_LBSS (node 0)                KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     128
    MultiPage Allocator                      608
    (7 row(s) affected)
    OBJECTSTORE_SNI_PACKET (node 0)          KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     2008
    MultiPage Allocator                      56
    (7 row(s) affected)
    OBJECTSTORE_SNI_PACKET (node 64)         KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     0
    MultiPage Allocator                      56
    (7 row(s) affected)
    OBJECTSTORE_SNI_PACKET (Total)           KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     2008
    MultiPage Allocator                      112
    (7 row(s) affected)
    OBJECTSTORE_SERVICE_BROKER (node 0)      KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     424
    MultiPage Allocator                      0
    (7 row(s) affected)
    OBJECTSTORE_LOCK_MANAGER (node 0)        KB
    VM Reserved                              32768
    VM Committed                             32768
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     4048
    MultiPage Allocator                      0
    (7 row(s) affected)
    OBJECTSTORE_LOCK_MANAGER (node 64)       KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     24
    MultiPage Allocator                      0
    (7 row(s) affected)
    OBJECTSTORE_LOCK_MANAGER (Total)         KB
    VM Reserved                              32768
    VM Committed                             32768
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    SinglePage Allocator                     4072
    MultiPage Allocator                      0
    (7 row(s) affected)
    Buffer Pool                              Value
    Committed                                1024000
    Target                                   1024000
    Database                                 793462
    Dirty                                    36258
    In IO                                    0
    Latched                                  0
    Free                                     171398
    Stolen                                   59140
    Reserved                                 0
    Visible                                  1024000
    Stolen Potential                         913660
    Limiting Factor                          17
    Last OOM Factor                          0
    Last OS Error                            0
    Page Life Expectancy                     262733
    (15 row(s) affected)
    Process/System Counts                    Value
    Available Physical Memory                69021696
    Available Virtual Memory                 8762135273472
    Available Paging File                    12716019712
    Working Set                              15196917760
    Percent of Committed Memory in WS        100
    Page Faults                              897824874
    System physical memory high              0
    System physical memory low               0
    Process physical memory low              0
    Process virtual memory low               0
    (10 row(s) affected)
    Procedure Cache                          Value
    TotalProcs                               4573
    TotalPages                               53712
    InUsePages                               27
    (3 row(s) affected)
    Global Memory Objects                    Pages
    Resource                                 412
    Locks                                    509
    XDES                                     219
    SETLS                                    8
    SE Dataset Allocators                    16
    SubpDesc Allocators                      8
    SE SchemaManager                         1169
    SE Column Metadata Cache                 991
    SQLCache                                 893
    Replication                              2
    ServerGlobal                             52
    XP Global                                2
    SortTables                               3691
    (13 row(s) affected)
    Query Memory Objects (internal)          Value
    Grants                                   0
    Waiting                                  0
    Available                                756700
    Current Max                              756700
    Future Max                               756700
    Physical Max                             756700
    Next Request                             0
    Waiting For                              0
    Cost                                     0
    Timeout                                  0
    Wait Time                                0
    (11 row(s) affected)
    Small Query Memory Objects (internal)    Value
    Grants                                   0
    Waiting                                  0
    Available                                12800
    Current Max                              12800
    Future Max                               12800
    (5 row(s) affected)
    Optimization Queue (internal)            Value
    Overall Memory                           6723993600
    Target Memory                            5965963264
    Last Notification                        1
    Timeout                                  6
    Early Termination Factor                 5
    (5 row(s) affected)
    Small Gateway (internal)                 Value
    Configured Units                         32
    Available Units                          32
    Acquires                                 0
    Waiters                                  0
    Threshold Factor                         380000
    Threshold                                380000
    (6 row(s) affected)
    Medium Gateway (internal)                Value
    Configured Units                         8
    Available Units                          8
    Acquires                                 0
    Waiters                                  0
    Threshold Factor                         12
    Threshold                                -1
    (6 row(s) affected)
    Big Gateway (internal)                   Value
    Configured Units                         1
    Available Units                          1
    Acquires                                 0
    Waiters                                  0
    Threshold Factor                         8
    Threshold                                -1
    (6 row(s) affected)
    Memory Pool Manager                      Pages
    Reserved Current                         0
    Reserved Limit                           913664
    (2 row(s) affected)
    Memory Pool (internal)                   Pages
    Allocations                              59136
    Predicted                                248311
    Private Target                           0
    Private Limit                            0
    Total Target                             972800
    Total Limit                              972800
    OOM Count                                0
    (7 row(s) affected)
    MEMORYBROKER_FOR_CACHE (internal)        Pages
    Allocations                              55358
    Rate                                     0
    Target Allocations                       779847
    Future Allocations                       0
    Overall                                  820800
    Last Notification                        1
    (6 row(s) affected)
    MEMORYBROKER_FOR_STEAL (internal)        Pages
    Allocations                              3778
    Rate                                     0
    Target Allocations                       728267
    Future Allocations                       0
    Overall                                  820800
    Last Notification                        1
    (6 row(s) affected)
    MEMORYBROKER_FOR_RESERVE (internal)      Pages
    Allocations                              0
    Rate                                     0
    Target Allocations                       820800
    Future Allocations                       189175
    Overall                                  820800
    Last Notification                        1
    (6 row(s) affected)
    DBCC execution completed. If DBCC printed error messages, contact your system administrator.

  • Sql server Memory usage

    Hi,
    How to find out the current utilization of Ram in sql server? and how to restrict the ram for sql server  windows 2008r2 with 64bit os?

     Hi,
    How to find out the current utilization of Ram in sql server? and how to restrict the ram for sql server  windows 2008r2 with 64bit os?
    Hi,
    Below query will give you memory utilized by SQL server
    select
    (physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
    (locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
    (total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
    process_physical_memory_low,
    process_virtual_memory_low
    from sys. dm_os_process_memory
    You can restrict only buffer pool by putting limit on MAX Server memory using below query
    sp_configure 'show advanced options' ,1
    go
    reconfigure
    go
    sp_configure 'max server memory MB',xxx --value you want to put
    go
    reconfigure
    Please note that even if yu put cap on max server memory still SQL server can consume more memory that max limit and this memory will be direct memory allocation done by windows for features like SQLCLR,XML,Stack threads, Linked servers.
    More details
    http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • SQL Developer - Memory Usage

    We have SQL Developer installed on our Citrix farm and we are facing hard times right now. Unfortunately SQL Developer is consuming in some cases more than 650 MB/session. And since we have on each site more than 50 users in same time, server gets exceeded very fast. Currently server is running Windows 2003 R2 edition x86. We know that this is bad and we are planning on switching on Windows Server 2008 R2. And here comes my questions:
    Will Windows Server 2008 R2 work more effectively with Java x64 and SQL Developer x64 and resolve our memory issues?
    Thank you.

    Hi,
    I have no idea if Windows Server 2008 runs Java applications better than 2003 but, regardless of which you run, here are a couple of ideas that may be of help:
    1. x32 Java/SQL Developer starts up with a smaller working set (246,000 KB) than x64 Java/SQL Developer (318,000 KB).
    2. Try tweaking the garbage collection algorithm, using Garbage-First:
    Re: Memory Leak or Bad Java Garbage Collector
    I ran across this (old) comment from a blog on blogs.msdn.com:
    Even though Windows Server 2008 R2 is exclusively a 64-bit operating system, 32-bit applications are
    supported by enabling the WoW64 optional feature. If this feature is not enabled and you try to run a
    32-bit application, the application will fail to execute. The WoW64 execution layer is an optional component
    that is installed by default on R2 releases after beta1. You can save resources by removing the feature if
    you are not going to be running 32-bit applications on your Server Core install. Regards,
    Gary
    SQL Developer Team

  • Pl/sql record - Memory usage

    Hi ,
    I'm using pl/sql record which hold 14,00,000 rows and process those rows one by one. Will this create memory problem in prodution?
    Here is the status of v$process
    SELECT spid, program,
    pga_max_mem max,
    pga_alloc_mem alloc,
    pga_used_mem used,
    pga_freeable_mem free
    FROM V$PROCESS
    WHERE addr='070000004DF60B18'
    SPID     PROGRAM     MAX     ALLOC     USED     FREE
    2326748     oracleax010     9629198358     9629132822     3623509662 5832704
    Thanks for your help!     
    kannan
    Edited by: user601042 on Sep 22, 2010 12:43 AM

    Actually in our design Global Temp table is not allowed..earlier each time we read data from table(14,00,000 rows one by one) and process those rows..This look long time for job to run. instead of that using bulk collect i'm collecting all 14,00,000 rows into collection(10000 rows each collect) and processing rows from collection and this reduced my process time to 1/5 of earlier. But its taking more memory..
    Used memory is 3GB ..Do we need to conside allocated momory or used memory?.If used memory is 3GB means fine?
    Thanks,
    kannan

  • DBCC CHECKDB failure, SQL 2012, There is insufficient system memory in resource pool 'internal' to run this query.

    Hey, guys!
    Tried to find an answer, but nothing works for me.
    So on one of servers when I am trying to run DBCC CHECKDB throws two errors
    Msg 8921, Level 16, State 1, Line 1
    Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
    Msg 701, Level 17, State 123, Line 1
    There is insufficient system memory in resource pool 'internal' to run this query.
    This is a VM hosted on Hyper-V server 2012 R2. VM has Windows Server 2012 R2 and SQL Server 2012 Std. VM had 8 GB of RAM, I increased it to 12GB (static, not dynamic), also I increased paging file size in Windows and size of TEMPDB also recreated TEMPDB.
    I also tried to restore the Database, which throws an error from another server. On that server DBCC CHECKDB works fine, but it didn't help - I still receive the same error.  Can you suggest, please?

    Hi,
    I agree with you. It is probably a memory issue. First, we need to verify if it is an OS memory issue or caused by SQL Server itself.
    Need to use Performance Monitor:
    SQLServer:Memory
    Memory
    Dynamic Management Views:
    sys.dm_os_sys_info
    sys.dm_exec_query_memory_grants
    1. Use performance monitor to check OS memory: available memory(MB) and monitor the OS memory status before the query and when running the query. If it does not change, I can exclude the OS memory factor. Then, I can conclude
    this memory issue was caused by SQL Server internal. Also, check if there is Memory leak on your system.
    2. Use the below script in SQL Server Management Studio and Result to Text.
    while(1=1)
    begin
    print getdate()
    print '*****sys.dm_exec_query_memory_grants******'
    select * from sys.dm_exec_query_memory_grants
    print 'DBCC memorystatus'
    dbcc memorystatus
    waitfor delay '00:00:01'
    end
    Then, check SQLServer:Memory-Granted Workspace Memory (KB) when the issue occurs which specifies the total amount of memory currently granted to executing processes, such as hash, sort, bulk copy, and index creation operations.
    And compared with the information got in
    sys.dm_exec_query_memory_grants.
    3. In addition, use sys.dm_os_sys_info
     to identify bpool_commit_target and bpool_commited.
    In SQL Server 2012, the columns have been renamed as
    committed_target_kb and committed_kb.
    committed_kb  represents the committed memory in kilobytes (KB) in the memory manager. Does not include reserved memory in the memory manager.
    committed_target_kb represents the amount of memory, in kilobytes (KB), that can be consumed by SQL Server memory manager. The target amount is calculated using a variety of
    inputs like:
    the current state of the system including its      load
    the memory requested by current processes
    the amount of memory installed on the computer
    configuration parameters
    If committed_target_kb is larger than
    committed_kb, the memory manager will try to obtain additional memory. If
    committed_target_kb is smaller than committed_kb, the memory manager will try to shrink the amount of memory committed. The
    committed_target_kb always includes stolen and reserved memory.
    MSSQLSERVER_701
    http://msdn.microsoft.com/en-us/library/aa337311.aspx
    An in-depth look at SQL Server Memory–Part 3
    http://blogs.msdn.com/b/sqljourney/archive/2013/11/02/10402729.aspx
    INF: Using DBCC MEMORYSTATUS to Monitor SQL Server Memory Usage
    http://support.microsoft.com/kb/271624/en-us
    Hope it helps.
    Tracy Cai
    TechNet Community Support

  • SQL Server Memory

    Hi All,
    I am not sure if this is a fair ask or no but this is something i want to learn much internals about sql server memory and how sql server responds to memory pressure and i wanted to see that practically.
    Environment : windows 2003, 4 GB physical RAM, SQL server 2005 sp4.
    Checking in if someone has some demo tsql scripts which can blow up memory so that i can setup the memory counters and monitor sql server memory usage.
    Did anyone has done this earlier?
    Thanks in advance.

    Why do I see “A significant part of sql server process memory has been paged out. This may result in performance degradation.” By SQL Server In spite of having above mechanism to detect the system level memory pressure and scale
    SQL Server memory?
    There are couple of situations where SQL Server Process working set might be paged out by Windows despite these memory resource notification mechanism.
    1.If windows is not sending the correct notifications to all listening processes at the right moment and thresholds
    2.If SQL Server is not responding fast enough to the low memory resource notification from Windows
    3.Conditions in Windows where working sets of all processes are trimmed
    4.Windows might decide to trim a certain percentage of working set of various or specific processes
    Above is from
    A significant part of SQL Server process memory has been paged out.
    Please use Marked as Answer if my post solved your problem and use
    Vote As Helpful, if a post was useful to help other user's find a solution quicker.

  • SQL server memory usase

    Hi Experts,
    Can anyone please tell me how can we check SQL server memory usages?
    Thanks in Advance

    Hi Experts,
    Can anyone please tell me how can we check SQL server memory usages?
    Thanks in Advance
    Can use Perfmon.DMV is the best.Will work for 2008 and above
    select
    (physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
    (locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
    (total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
    process_physical_memory_low,
    process_virtual_memory_low
    from sys. dm_os_process_memory
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • SQL Server 2012- Memory Leak Issue

    Team,
    We are running a Mission Critical Application on SQL Server 2012 SP2(11.0.5058) which is configured on Always ON Synchronous mode. Offlate due to heavy development work, Application team have come up with stating memory issues. I have analysed all the areas
    and everything looks normal. Please suggest if we have to patch the latest CU4 for SQL Server 2012 SP2. 
    The checks were performed on the below areas:
    - Errorlog, System Logs - No errors reported.
    - There are close to 8 Databases hosted on the instances which are all configured for AlwaysON. SQL Server is running on VM Infrastructure and the total physical memory allocated is 96GB out of which SQL is capped for 92GB. 
    -The Page Life Expectancy is healthy and is showing a greater number. There are no Signal waits either or pending memory grants. 
    - The writes are more than reads for one of the databases which is flagged with application team. There are no blockings & Deadlocks.
    Please suggest me the future course of action and your inputs are much appreciated.
    Best Regards,
    Sharath 

    Actual issue is- Application team have reported a memory leak and their builds have significantly slowed down. They suspect that its Database memory leak. However I have verified from database end and gave the above inputs. 
    The AOAGs are good. I was looking for any pointers whether there are any bugs which is related to memory leaks in SQL Server 2012.  I know all of them are addressed with SQL Server 2012 SP2. 
    Application team has NO idea about SQL Server do they ? And to say SQL Server has memory leak you have to actually prove it did they showed any proof. Its common for application team to say SQL Server is leaking memory because they are unaware about fact
    by default SQL Server would take as much memory as possible and would release when SQLOS asks it to do so. This might give sign that it is leaking memory BUT IT IS NOT.
    As you already said AOAG is working fine so I am presuming there is nothing much to worry. To monitor memory usage in SQL Server 2012 you can use below counters
    SQL Server: Memory Manager-- Target Server Memory (KB)
    SQL Server: Memory Manager--Total Server Memory (KB)
    SQL Server: Memory Manager- Free Memory (KB)
    SQL Server: Memory Manager--Database Cache Memory (KB)
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Wiki Article
    MVP

  • HIGH memory usage in Perf Counters but LOW by SQL components

    Hi all,
    Our SQL Server has the following specs:
    OS: Windows Server 2008 R2 Enterprise Edition SP1+Cumulative Updates
    RAM: 128GB
    SQL Server: 2012, Enterprise (SP2), Core-based Licensing (64-bit)
    Max Memory Setting: Limited to 123GB
    I used performance counters to see memory usage by SQL Server:
    SQLServer:MemoryManager:TargetServerMemory(KB)=125,952,000
    SQLServer:MemoryManager:TotalServerMemory(KB)=125,634,000
    SQLServer:BufferManager:PageLifeExpectancy=104,000
    When I use SSMS report (Memory Consumption) and navigate to "Memory usage by components", the sum of "Allocated memory (KB)" is about 34GB and is not equal to TotalServerMemory perf counter. 
    Please help me to understand relation between this report and perf counters mentioned above. 
    Many thanks in advance.
    Leila

    Process/System Counts                    Value
    Available Physical Memory                1490161664
    Available Virtual Memory                 8599063212032
    Available Paging File                    12067610624
    Working Set                              128870092800
    Percent of Committed Memory in WS        100
    Page Faults                              240261318
    System physical memory high              1
    System physical memory low               0
    Process physical memory low              0
    Process virtual memory low               0
    (10 row(s) affected)
    Memory Manager                           KB
    VM Reserved                              191481084
    VM Committed                             125669808
    Locked Pages Allocated                   0
    Large Pages Allocated                    0
    Emergency Memory                         1024
    Emergency Memory In Use                  16
    Target Committed                         125952008
    Current Committed                        125669808
    Pages Allocated                          44388280
    Pages Reserved                           1928
    Pages Free                               77023672
    Pages In Use                             16043264
    Page Alloc Potential                     103611136
    NUMA Growth Phase                        0
    Last OOM Factor                          0
    Last OS Error                            0
    (16 row(s) affected)
    Memory node Id = 0                       KB
    VM Reserved                              191479484
    VM Committed                             62784472
    Locked Pages Allocated                   0
    Pages Allocated                          20930080
    Pages Free                               39219960
    Target Committed                         62975992
    Current Committed                        62784472
    Foreign Committed                        1118440
    Away Committed                           0
    Taken Away Committed                     0
    (10 row(s) affected)
    Memory node Id = 1                       KB
    VM Reserved                              1536
    VM Committed                             62885316
    Locked Pages Allocated                   0
    Pages Allocated                          23458200
    Pages Free                               37803712
    Target Committed                         62975992
    Current Committed                        62885320
    Foreign Committed                        92596
    Away Committed                           0
    Taken Away Committed                     0
    (10 row(s) affected)
    Memory node Id = 64                      KB
    VM Reserved                              0
    VM Committed                             20
    Locked Pages Allocated                   0
    (3 row(s) affected)
    MEMORYCLERK_SQLGENERAL (node 0)          KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          184448
    (6 row(s) affected)
    MEMORYCLERK_SQLGENERAL (node 1)          KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          464
    (6 row(s) affected)
    MEMORYCLERK_SQLGENERAL (Total)           KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          184912
    (6 row(s) affected)
    MEMORYCLERK_SQLBUFFERPOOL (node 0)       KB
    VM Reserved                              51979512
    VM Committed                             3382604
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          14168056
    (6 row(s) affected)
    MEMORYCLERK_SQLBUFFERPOOL (node 1)       KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          18436712
    (6 row(s) affected)
    MEMORYCLERK_SQLBUFFERPOOL (Total)        KB
    VM Reserved                              51979512
    VM Committed                             3382604
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          32604768
    (6 row(s) affected)
    MEMORYCLERK_SQLQUERYEXEC (node 0)        KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          18056
    (6 row(s) affected)
    MEMORYCLERK_SQLOPTIMIZER (node 0)        KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          1736
    (6 row(s) affected)
    MEMORYCLERK_SQLUTILITIES (node 0)        KB
    VM Reserved                              14656
    VM Committed                             14656
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          10256
    (6 row(s) affected)
    MEMORYCLERK_SQLUTILITIES (node 1)        KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          7952
    (6 row(s) affected)
    MEMORYCLERK_SQLUTILITIES (Total)         KB
    VM Reserved                              14656
    VM Committed                             14656
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          18208
    (6 row(s) affected)
    MEMORYCLERK_SQLSTORENG (node 0)          KB
    VM Reserved                              19712
    VM Committed                             19712
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          19016
    (6 row(s) affected)
    MEMORYCLERK_SQLSTORENG (node 1)          KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          12824
    (6 row(s) affected)
    MEMORYCLERK_SQLSTORENG (Total)           KB
    VM Reserved                              19712
    VM Committed                             19712
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          31840
    (6 row(s) affected)
    MEMORYCLERK_SQLCONNECTIONPOOL (node 0)   KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          1824
    (6 row(s) affected)
    MEMORYCLERK_SQLCONNECTIONPOOL (node 1)   KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          1144
    (6 row(s) affected)
    MEMORYCLERK_SQLCONNECTIONPOOL (Total)    KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          2968
    (6 row(s) affected)
    MEMORYCLERK_SQLCLR (node 0)              KB
    VM Reserved                              12606272
    VM Committed                             33460
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          82736
    (6 row(s) affected)
    MEMORYCLERK_SQLCLRASSEMBLY (node 0)      KB
    VM Reserved                              5096
    VM Committed                             5096
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          0
    (6 row(s) affected)
    MEMORYCLERK_SQLSERVICEBROKER (node 0)    KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          3088
    (6 row(s) affected)
    MEMORYCLERK_SQLHTTP (node 1)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          8
    (6 row(s) affected)
    MEMORYCLERK_SNI (node 0)                 KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          128
    (6 row(s) affected)
    MEMORYCLERK_SNI (node 1)                 KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          112
    (6 row(s) affected)
    MEMORYCLERK_SNI (node 64)                KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          16
    (6 row(s) affected)
    MEMORYCLERK_SNI (Total)                  KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          256
    (6 row(s) affected)
    MEMORYCLERK_FULLTEXT (node 0)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          384
    (6 row(s) affected)
    MEMORYCLERK_SQLXP (node 0)               KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          16
    (6 row(s) affected)
    MEMORYCLERK_BHF (node 0)                 KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          224
    (6 row(s) affected)
    MEMORYCLERK_BHF (node 1)                 KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          112
    (6 row(s) affected)
    MEMORYCLERK_BHF (Total)                  KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          336
    (6 row(s) affected)
    MEMORYCLERK_SQLQERESERVATIONS (node 0)   KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          2064
    (6 row(s) affected)
    MEMORYCLERK_XE_BUFFER (node 0)           KB
    VM Reserved                              3072
    VM Committed                             3072
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          0
    (6 row(s) affected)
    MEMORYCLERK_XE_BUFFER (node 1)           KB
    VM Reserved                              1536
    VM Committed                             1536
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          0
    (6 row(s) affected)
    MEMORYCLERK_XE_BUFFER (Total)            KB
    VM Reserved                              4608
    VM Committed                             4608
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          0
    (6 row(s) affected)
    MEMORYCLERK_XTP (node 0)                 KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          16
    (6 row(s) affected)
    MEMORYCLERK_HOST (node 1)                KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          320
    (6 row(s) affected)
    MEMORYCLERK_SOSNODE (node 0)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          87696
    (6 row(s) affected)
    MEMORYCLERK_SOSNODE (node 1)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          58688
    (6 row(s) affected)
    MEMORYCLERK_SOSNODE (node 64)            KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          2600
    (6 row(s) affected)
    MEMORYCLERK_SOSNODE (Total)              KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          148984
    (6 row(s) affected)
    MEMORYCLERK_SOSOS (node 0)               KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          192
    (6 row(s) affected)
    MEMORYCLERK_SOSMEMMANAGER (node 0)       KB
    VM Reserved                              265288
    VM Committed                             265176
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          0
    (6 row(s) affected)
    MEMORYCLERK_FULLTEXT_SHMEM (node 0)      KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              768
    SM Committed                             768
    Pages Allocated                          0
    (6 row(s) affected)
    MEMORYCLERK_SQLSERVICEBROKERTRANSPORT (node 0) KB
    VM Reserved                                    0
    VM Committed                                   0
    Locked Pages Allocated                         0
    SM Reserved                                    0
    SM Committed                                   0
    Pages Allocated                                320
    (6 row(s) affected)
    MEMORYCLERK_FSAGENT (node 0)             KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          24
    (6 row(s) affected)
    MEMORYCLERK_FILETABLE (node 0)           KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          72
    (6 row(s) affected)
    MEMORYCLERK_XE (node 0)                  KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          6368
    (6 row(s) affected)
    MEMORYCLERK_SQLLOGPOOL (node 0)          KB
    VM Reserved                              0
    VM Committed                             0
    Locked Pages Allocated                   0
    SM Reserved                              0
    SM Committed                             0
    Pages Allocated                          8328
    (6 row(s) affected)

  • Sql memory usage increase each time win app runs

    Hi,
    Sql memory usage increases each time when win app runs. Why does it work like this? Is it normal ?
    I restart SQL Server 2012. Only my win app uses SQL server.
    First run of winapp.
    start memory usage : 211.800 KB
    close memory usage: 528.136 KB
    Second run of xaf app.
    start memory usage : 528.136 KB
    close memory usage: 996.844 KB
    Third run of xaf app
    start memory usage : 996.844 KB
    close memory usage: 997.640 KB
    Fourth run of xaf app
    start memory usage : 997.640 KB
    close memory usage: 1.104.864 KB

    Hi,
    Sql memory usage increases each time when win app runs. Why does it work like this? Is it normal ?
    Yes, it is perfectly normal for SQL Server to acquire and hold onto large amounts of memory indefinitely.  This memory improves performance by avoiding disk I/O, query plan compilation and costly memory management. 
    On a dedicated SQL Server you should usually let SQL Server dynamically manage memory.  It will release memory if it detects memory pressure.  But if you often run other applications on the server than need significant amounts of memory (e.g. IIS,
    application services), you may want to set max server memory as suggested.
    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

  • High memory usage in SQL Servers

    Hi,
    I have few SQL servers which are having memory utilization more than 95% when checked in task manager.
    Servers OS - Windows server 2008 R2
    SQL Sever 2008 and SQL Server 2012
    AWE option is not enabled, Min memory setting  - 1 GB and Max memory setting - 80% of the total memory in server.
    SQL process is using less than max memory, when checked in task manager. So i was thinking where is remaining memory.
    Used RAMMAP tool and found memory in AWE, even if i disabled AWE in SQL Server. Please let me know how to avoid AWE.

    Hi,
    Task manager does not always show you correct value so I would advise you not to loot at task manager but in this case since you SQL Server service account does not have Locked pages in memory privilege(LPIM) task manager can be referred
    please use below query to see SQL Server memory utilization
    select
    (physical_memory_in_use_kb/1024)Memory_usedby_Sqlserver_MB,
    (locked_page_allocations_kb/1024 )Locked_pages_used_Sqlserver_MB,
    (total_virtual_address_space_kb/1024 )Total_VAS_in_MB,
    process_physical_memory_low,
    process_virtual_memory_low
    from sys. dm_os_process_memory
    Is your SQL server 64 bit version, then no need to enable AWE option.
    Its totally normal behavior for SQL Server to utilize memory. It can also utilize memory greater that what is limit in max server memory setting as this only controls buffer pool allocation.
    You can reduce max server memory value IF you really want SQL Server memory utilization in tak manager to come down. But I would again say its normal.
     What is max server memory value anyway?
    How much you have left for OS on atleast 5-6 G id required for OS. Value may vary.
    >>SQL process is using less than max memory, when checked in task manager. So i was thinking where is remaining memory
    SQL Server caches memory to store as much data and index pages(in memory)  as possible to avoid any physical I/O which is costly and once taken memory it will not release unless SQLOS asks it to do so . It will start trimming its mmeory consumption when
     SQLOS says it to do because of some memory pressure or other requirement. The process is totally dynamic and is managed perfectly so you dont need to worry.
    More about SQL Server memory and troubleshooting
    http://social.technet.microsoft.com/wiki/contents/articles/22316.sql-server-memory-and-troubleshooting.aspx
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • How to analyse the main memory usage in SAP ERP systems?

    Dear expert,
    I'm doing a research work about analysing the main memory usage in SAP ERP systems.
    I would like to find out what is load in buffers and when. That means, which process have the control of these memories and which are always performing something, tables loaded, and so on. Becuase I tried to isolate the space needed by a simple webservice call (create one material) in my test system, but even after a $SYN there are something stored in the buffers. I use a BAPI to avoid the execution of the SAPGUI and its repercussion in the system (I know the BAPI called uses resources too, but when I run this BAPI to get the statistics, it's like ST02, I get different values). Could someone help me or recommend something specific to read? Thanks a lot in advance.

    Dear expert,
    Thanks a lot for your answer. The point is now that I want to isolate the memory used by a webservice that I call, I mean, I would like to know how many memory is this webservice using in each buffer. And could you tell me where could I read something about the order that things happen in SAP System when a webservice is called (always memory related), that's which steps are done to store data in buffers and so on. Thanks in advance.

Maybe you are looking for

  • Reg: Table creation for generic source

    Hai, I tried to create generic data source using a table that I created. But when I tried to enter entries into the table using se16 transaction, one field is not at all coming. I didnt understand why this field is not coming. I checked the enhanceme

  • How do I play movie in iTunes on my TV?

    I don't have Apple TV but in the past, I've been able to play a movie I made myself on my monitor that also is a TV (i.e., my Sony Trinitron TV). I tried out the video rental thing in iTunes and I canNOT get it to display on my TV monitor. Yes, I hav

  • Function Module for getting the System time.

    Hello All, Which is the Function Module used in APO to get the system time? Thanks for your response in advance. Regards, Chirag

  • How to implement this functionality?

    hi, I want to use a thread to send all message centrally. The thread will check if the internal queue is empty. If the queue isn't empty, it sends the message, otherwise, it yields. The code snippet is as the following.   public void run()     logger

  • Unable to connect to AE 802.11n through airport utility -despite resetting

    Hi all, I do realize that there are a number of threads adressing what seems to be my problem, but none of the solutions have worked for me. I have a 2 year old AE 802.11n that has given me flawless wireless network for a long time now. I have for so