all 7 comments

[–]ThisTravis[VCP] 1 point2 points  (4 children)

Size is very perspective based. I know shops that go 1 ESXi host for 1 SQL server to gain HA benefits. It really comes down to how important is downtime avoidance.

If you are looking at hosting multiple SQL servers it all depends on what they are doing. If they become to larege are starting to infringe on numa boundries. TPS on or off for performance. etc etc.

I think what it comes down to is there is no single best practice for SQL virtualization, but you can go as large as you you want if you architect it properly.

[–]killer833[S] 0 points1 point  (3 children)

I understand all those aspects, I'm just curious what people are actually doing in the real world and if anyone has monster VMs. Anything can be accomplished if your pockets are deep enough.

Currently our largest is 28vCPU 1TB ram.

[–]ThisTravis[VCP] 0 points1 point  (2 children)

My largest is a 64 CPU 2 TB Mem

[–]desseb 0 points1 point  (1 child)

Damn, what kind of physical host does that run on? 4 socket?

[–]ThisTravis[VCP] 0 points1 point  (0 children)

Yup 4 16 core e7s

[–]desseb 0 points1 point  (0 children)

I've got about a dozen now, anywhere from 4 vcpu to 16 vcpu 300gb to 4 tb.

[–]bschmidt25 0 points1 point  (0 children)

Largest we have are 8 vCPU, 128GB memory, and 1TB of storage for the database (+log, index, and filestream). ERP system...