StephenNL (7/8/2014)
Here some data of our vm:NUMBER OF VM: 1
RAM: 16 GB (static)
CORES: 4
HD: IDE, 150 GB.
Filesize (mdf): 5.92 GB
Filesize (log): 3.93 GB
The capacity of the cpu (VM) during the query is runnig is approx. 2 %.
I guess, the reason is not the CPU for being that slow. 😉
Maybe, we should choose another network configuration, because part of the work is done by the client.
Any idea ?
firstly - assuming you have no other workloads on that machine kicking CPU significantly over 25%, I would cut to 1 CPU. If possible, I'd also consider whether this could be consilidated with other servers. Too many cores on a VM can actually degrade performance.
I'd also get your VMWare admin to swear blind you're not being ballooned. If you're new to SQL Server on VMs I'd have a look at these;
http://www.brentozar.com/sql/virtualization-best-practices/
also Jonathan Keyannes on this issue on PluralSight (not free this one $29 pcm) and also Brent's paid for VM and SAN training video ($400 ish IIRC) if you're feeling flush or can get the company to swing for it. You are going to find stuff in there that's going to surprise your VM/SAN admin(s). As mine have found out.
It's NOT like running a File Server, SQL Server "Doesn't Play Nice With Others" on these systems
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.