locked
Alert: SSAS 2008: Memory configuration conflict with SQL Server RRS feed

  • Question

  • hallo

    i give this errore 

    please help my what i need ?

    thanks

    Source: WSA
    Path: SQL.mydomain.com
    Alert: SSAS 2008: Memory configuration conflict with SQL Server
    New
    The SQL Server Analysis Services instance TotalMemoryLimit configuration setting (25.5983390808105 GB) leaves 6.39958572387695 GB out of 31.9979248046875 GB for the operating system and SQL Server, which is below the configured threshold for the alert.
                Total memory on the server: 31.9979248046875 GB
                Total memory usage: 20.4979095458984 GB
                Memory used by non-SSAS processes: 20.430103302002 GB
                Memory used by SSAS: 6.78062438964844E-02 GB
                SSAS Memory Limit Low: 20.7986507415771 GB (64.9999988078298%)
                SSAS Memory Limit High: 25.5983390808105 GB (79.9999976156596%)
    Last modified by: System
    Last modified time: 5/9/2015 11:10:12 PM
    Alert description: The SQL Server Analysis Services instance TotalMemoryLimit configuration setting (25.5983390808105 GB) leaves 6.39958572387695 GB out of 31.9979248046875 GB for the operating system and SQL Server, which is below the configured threshold for the alert.
                Total memory on the server: 31.9979248046875 GB
                Total memory usage: 20.4979095458984 GB
                Memory used by non-SSAS processes: 20.430103302002 GB
                Memory used by SSAS: 6.78062438964844E-02 GB
                SSAS Memory Limit Low: 20.7986507415771 GB (64.9999988078298%)
                SSAS Memory Limit High: 25.5983390808105 GB (79.9999976156596%)


    אם תגובתי פתרה את בעייתך - לחץ/י, על "סמן כתשובה" ליד סימן ה V הירוק.

    Sunday, May 10, 2015 8:41 AM

Answers

  • The corresponding downloads are available at:
    The System Center Management Pack for SQL Server Analysis Services enables the discovery and monitoring of SQL Server Analysis Services Engines, Databases and Partitions.
    These Management Pack are designed to be run by Operations Manager 2012 RTM or higher.
     
    The monitoring provided by these management pack includes performance, availability and configuration scenarios, as well as performance data collection. All monitoring workflows have predefined thresholds and associated knowledge base articles.
    In addition to the health monitoring capabilities, these management pack includes dashboards, diagram, state, performance and alert views.
     
     
    Feature Summary for SQL Server 20xx Analysis Services
    The following list gives an overview of features introduced by System Center Operations Manager Management Pack for SQL Server 20xx Analysis Services. Please refer to the SQL Server 20xx Analysis Services Management Pack Guide for more details.

    SSAS Instance level monitoring
    • Service state
    • Memory Configuration Conflict with SQL Server
    • TotalMemoryLimit Configuration
    • Memory Usage
    • Memory Usage on the Server
    • Processing Pool Job Queue length
    • Query Pool Queue length
    • Default Storage Free Space
    • CPU utilization
    SSAS Database level monitoring
    • Database Free Space
    • Blocking Duration
    • Blocking Session Count
    SSAS Partition level monitoring
    • Partition Storage Free Space
    A number of performance collection rules

    http://dba.stackexchange.com/questions/29403/how-to-balance-sql-server-memory-with-sql-server-analysis-services-memory

     It also gives some high-level information about the way SSAS manages memory, process memory, instances, languages, and thread pools.

    Server Properties

    AggregationMemoryLimitMax

    AggregationMemoryLimitMax is a server property that controls the maximum amount of memory that can be used for SSAS aggregation processing. This value is expressed as a percentage of total memory if the value is less than 100, or an absolute value of bytes if the value is greater than 100. The default value is 80, which indicates that a maximum of 80% of the total physical memory can be used for SSAS aggregation processing.

    Check sql memory required by 

    https://www.sqlskills.com/blogs/jonathan/how-much-memory-does-my-sql-server-actually-need/



    Sunday, May 10, 2015 11:55 AM
  • Hi eyalcohen,

    According to your description, you get the alert about conflict memory configuration between SSAS and SQL Server. Right?

    In SQL Server, the relational database engine can consume memory resources on a machine also running SSAS. So it may cause competition for physical memory by both consumers of the same fixed resource. In this scenario, one service need to allow enough resource for another so that both of them can perform well. For optimizing this kind of problem, please do the following approaches:

    • Lower the SSAS instance(s) TotalMemoryLimit configuration setting.

    • Adjust the SQL Server instance(s) max memory limit setting

    • Increase available memory on the server.

    • Set appropriate threshold for the alert 

    After that you can install Management Pack as Dinesh mentioned.

    Regards,


    Simon Hou
    TechNet Community Support


    Tuesday, May 12, 2015 2:48 PM

All replies

  • The corresponding downloads are available at:
    The System Center Management Pack for SQL Server Analysis Services enables the discovery and monitoring of SQL Server Analysis Services Engines, Databases and Partitions.
    These Management Pack are designed to be run by Operations Manager 2012 RTM or higher.
     
    The monitoring provided by these management pack includes performance, availability and configuration scenarios, as well as performance data collection. All monitoring workflows have predefined thresholds and associated knowledge base articles.
    In addition to the health monitoring capabilities, these management pack includes dashboards, diagram, state, performance and alert views.
     
     
    Feature Summary for SQL Server 20xx Analysis Services
    The following list gives an overview of features introduced by System Center Operations Manager Management Pack for SQL Server 20xx Analysis Services. Please refer to the SQL Server 20xx Analysis Services Management Pack Guide for more details.

    SSAS Instance level monitoring
    • Service state
    • Memory Configuration Conflict with SQL Server
    • TotalMemoryLimit Configuration
    • Memory Usage
    • Memory Usage on the Server
    • Processing Pool Job Queue length
    • Query Pool Queue length
    • Default Storage Free Space
    • CPU utilization
    SSAS Database level monitoring
    • Database Free Space
    • Blocking Duration
    • Blocking Session Count
    SSAS Partition level monitoring
    • Partition Storage Free Space
    A number of performance collection rules

    http://dba.stackexchange.com/questions/29403/how-to-balance-sql-server-memory-with-sql-server-analysis-services-memory

     It also gives some high-level information about the way SSAS manages memory, process memory, instances, languages, and thread pools.

    Server Properties

    AggregationMemoryLimitMax

    AggregationMemoryLimitMax is a server property that controls the maximum amount of memory that can be used for SSAS aggregation processing. This value is expressed as a percentage of total memory if the value is less than 100, or an absolute value of bytes if the value is greater than 100. The default value is 80, which indicates that a maximum of 80% of the total physical memory can be used for SSAS aggregation processing.

    Check sql memory required by 

    https://www.sqlskills.com/blogs/jonathan/how-much-memory-does-my-sql-server-actually-need/



    Sunday, May 10, 2015 11:55 AM
  • Hi eyalcohen,

    According to your description, you get the alert about conflict memory configuration between SSAS and SQL Server. Right?

    In SQL Server, the relational database engine can consume memory resources on a machine also running SSAS. So it may cause competition for physical memory by both consumers of the same fixed resource. In this scenario, one service need to allow enough resource for another so that both of them can perform well. For optimizing this kind of problem, please do the following approaches:

    • Lower the SSAS instance(s) TotalMemoryLimit configuration setting.

    • Adjust the SQL Server instance(s) max memory limit setting

    • Increase available memory on the server.

    • Set appropriate threshold for the alert 

    After that you can install Management Pack as Dinesh mentioned.

    Regards,


    Simon Hou
    TechNet Community Support


    Tuesday, May 12, 2015 2:48 PM