Post reply

Moving Beyond the Reboot: Finding the Culprit Behind Memory Pressure

  • September 25, 2026 at 12:00 am

    #4970612

    Comments posted to this topic are about the item Moving Beyond the Reboot: Finding the Culprit Behind Memory Pressure

  • September 25, 2026 at 7:37 pm

    #5032005

    Unless I missed something, it appears that you've not mentioned the version nor the edition of SQL Server this happened on nor how much overall RAM was available in the system nor how much RAM was allocated to SQL server, etc.  It may be that the real problem is that your sever might simply be memory starved even for the Standard Edition.

     

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • September 25, 2026 at 8:49 pm

    #5032277

    Hi Jeff, thank you for your comment. I have one SQL Server 2022 Standard with 96 GB RAM, and another SQL Server 2025 Enterprise with 200 GB RAM. In one server, there was one SSAS instance with the default memory settings. In the other server, there were two SSAS instances, one Multidimensional and the other Tabular, with the default memory settings. In both cases, fine tuning the SSAS memory settings resolved the problem; the problem was not caused by the SQL Server instance.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply