2

We have launched Linux with SQL Server standard edition for production environment, but the memory restriction feature in SQL Server is not working properly.

The server has a total of 32 GB of RAM. We initially allocated 25 GB to SQL Server in mssql.conf and experienced crashes due to the OOM killer.

We have since reduced this to 18 GB memory, but it's still utilizing all the server memory, and the service is eventually killed.

What else can we do to prevent the SQL Server service from being killed by the OOM Killer?

Improve this question
0

1 Answer 1

Reset to default
1

Are there are other applications / workloads running on the server when SQL Server gets killed?

If Linux detects memory pressure, SQL Server will be the easy target - even if it's staying with the 18 GB limit you set. Imagine SQL Server using 18GB, and 3 other applications using 6 GB each. The Linux kernel will target the SQL Server process to free up RAM, because it is using the most of any single process.

You should monitor memory usage by all apps on the box leading up to the crash. If other apps are using a lot of RAM, you should consider either:

  • removing them, or
  • further reducing the memory available to SQL Server

If SQL Server is really exceeding its limits, your best bet is likely to contact Microsoft support.

For a real life example, see this article from SQL Server support for recommendations on avoiding the OOM Killer:

How to safeguard SQL Server on Linux from OOM-Killer

Improve this answer
1
  • Hi Josh , Thanks much . No other applications are running in SQL Server Machine . We have increased the machine type to fine the issue , still we are seeing much utilization in SQL Server . We will plan to contact MS Support
    – Selva
    Commented Apr 15, 2019 at 7:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.