Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Understanding SQL Monitoring in SAM

Good Day Guys

I just have a question or two for my own sanity on understanding my SolarwindsOrion Database.

For what reason would the SQL Server Process only use 4GB of RAM but looking at the AppInsight for SQL it shows differently.

Find more posts tagged with

Accepted answers

All comments

aLTeReGo

Based on the data shown it appears that SQL may be installed on a 32bit operating system, or that you are using a 32bit version of SQL installed on a 64bit operating system.

scvvuuren

Thanks aLTeReGo

That is what I thought as well initially, but they are both x64 platform.

Screenshot's below. So I am wondering why it would report 4GB RAM usage for the process.

aLTeReGo

Can you trying changing the "Platform to run polling job on" for that application from x86 to x64, wait a few polling periods and see if that resolves the issue?

scvvuuren

Hi aLTeReGo

Changed it this morning, but the results remains the same though.

aLTeReGo

Are there multiple SQL Instances running on this server? Also, what does Task Manager report for memory (Memory - Working Set). A screenshot of all memory usage related to this process would be helpful.

scvvuuren

The Server is physical and it only runs SolarwindsOrion Database Instance.

We also run the Solarwinds Netflow DB tool on this server.

Server Specifications is as follows.

2x 4 Core 3.3 GHz CPU (we switched of Hyper Threading to test possible performance issue)

8x SSD HDD in a RAID 10 split into multiple partitions for logs, DB, OS and FlowsDB.

64GB RAM but SQL is limited to 48GB RAM.

Screenshots of Task Manager, Resource Manager and some results from Ignite.

aLTeReGo

At this point I'm at a complete loss to explain why the process monitor is showing only 4GB of memory consumed when all other data is to the contrary. The exception being the Task Manager in your screenshot above, but that is because you are showing "Memory (private working set) and not "Working set (memory)". At this point I would ask you to verify that you're running the latest SAM 6.1.1 release, and if not please upgrade. If you're already on SAM 6.1.1 or after upgrading you're still seeing the same issue then please open a case with Support so we can chase this down.