Link to home
Start Free TrialLog in
Avatar of John McDermott
John McDermottFlag for United States of America

asked on

VMware VM settings for Windows Database Server

We have a serer that currently has 3 pretty decent size drives that are on the same datastore and DBA is reporting performance issues and wanted to start with basics and I'm thinking that we separate the disk to different datastores to see if any change and curious what your opinion on the matter would be?

VMware does not really seem to have a great opinion on it and not 100% this is a straightforward answer but wanted to at least begin the dialogue.

VMware 6.5
Storage is VNX block with multiple mixed raid arrays and fast caching enabled
Windows Server 2012
SQL 2012 Enterprise sp4


JM
Avatar of arnold
arnold
Flag of United States of America image

Andrew has many articles that you might find useful.
https://www.experts-exchange.com/members/hanccocka.html/profileContributionsTab.async
You provided some information but it is not clear ......
What is the complaint.
How the VM is defined, number of vCPU's memory allocation. how big is the database?

VNX block, dedicated network?

Do you have VCSA through which you manage the host...... or you have a single host.
Your question seems to be more geared towards prioritization.
i.e. if you have multiple VMs, do they have equal priority on the CPU, Memory and storage.

one option to improve sql VM performance is to prioritize CPU, Memory, and storage for it.

Depending what the other VMs are you could lower a prioritization for some VMs without impacting detectable performance by the user.
Sql is a more intensive task where there are requests and responses flying back and forth and a delay which multiplies by the number of the back and forth events,,,,,,,

Presumably all your VMs are not in normal and equal resource distribution, changing the sql to a higher prioritization for memory and CPU.
Though I am relying that the DBA already took steps to optimize the queries, tables.

You should get a clearer understanding from the DBA what he means by, "performance issues"
Have him look at the execution plan of the queries....
Avatar of John McDermott

ASKER

OK,  i did skip around a bit - its a new issue for the processing.

we are running DRS and have an affinity rule to stay on a specific host which is monstrous for CPU and Memory.  we did not set shares or values for memory or cpu.

i'm reviewing the cpu and memory allocation and verify any reserved/limit/shares on cpu and memory - new area for me.

i'm certain this VM is overprovisioned?
over provisioning could create problems much like under provisioning.  One thing I would recommend in SQL is limit how much memory the process users in sql configuration.  It will consume all memory if you let and starve the OS.  All our instances have a cap.

You may want to look at how you created your drives, I think ours have 5, os, data, logs, temp and backups

You mention decent size databases, what does that look like, we talking 100 gigs or 100 terabytes?
if this is SQL VMware has a document....of best practices...which was written in April 2019


ARCHITECTING MICROSOFT SQL SERVER ON VMWARE VSPHERE® Best Practices Guide


Compare your setup of your VM with it....

Ask your DBA, how many IOPS does the database require ?

How many IOPS can your datastores perform ?

Spliting the disks across multiple datastores only makes sense if the datastores are on different tiered storage and can provide faster access.
ok, thanks so much everyone - were still gathering information.

At this point the server has 3 disks on same datastore and the memory and cpu are kind of standard and not really specified for the SQL server. it s Data  Warehouse  server and has grown over the past 2 years very significantly.
The DBA should recheck whether the queries are optimized execution plan.
Warehouse  data ....
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.