Skip to main content

Help! SQL Server is eating my memory.

Some of my team members were complaining that Team Foundation Server was really slow. So assigned as the 'TFS guru', I was the ultimate victim to look into the issue.
As I logged on the TFS server (and waited a looooong time), I noticed in the Task Manager that CPU usage was rather normal but all the memory was used and an enormous page file was eating up the hard disk space.After som sorting magic on the Mem usage column I saw that sqlservr.exe was using all the memory. More than 2 gigs of Mem Usage seems a little bit over the edge.
There were two things that helped me investigate the issue.

The first one are following commands; DBCC MemoryStatus and DBCC MemUsage
Second you can have a look at the huge amount of SQL Server performance counters that can help finding the problem.

But these didn't help me to pinpoint the exact problem.

One of my colleagues suggested that SQL Server was probably using all this memory because it prefers caching the data in memory over doing a lot of disk I/O (which sounded logical). So I opened up the SQL Server Management Studio and had a look at the properties of the database server.
I browsed to the Memory page where I limited the Maximum server memory and everything worked smoothly.
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more