Virtualized or physical?

Hi!

We are debating whether we should go physical or virtualized with our SolarWinds Orion environment. We used to have a physical failover cluster on a MSSQL Standard Edition license. We are now running on a virtualized environment on a single node. We are discussing which direction to go; virtualized with AlwaysOn, or go back to our physical failover-cluster. And furthermore, we are discussing whether we should upgrade to a MSSQL Enterprise Edition license.

Our environment is currently running with 55000 elements and 285000 SAM component. Zero downtime is very important.

We are having a hard time finding any metrics that directly indicate a need to go virtual, and the same for upgrading to Enterprise. We are aware that the limitation on memory and CPU cores on a standard edition might be a bottleneck, but can't seem to find any direct proof that upgrading would justify the cost of upgrading to Enterprise.

Has anyone been in the same situation? And if so, would you recommend virtual or physical, and what would your take on Standard vs Enterprise be?

Parents
  • Hi  ,
    In 2015, our Solarwinds monitoring solution used a physical server to monitor the Virtual Infrastructure running on VMware.

    Now, it has been converted to a fully virtualised environment on VMware. Set up the Affinity rule to separate the Database and Polling Engines VMs to a different host to avoid resource contention and redundancies.

    The most important thing here is the dedicated or separate SQL Server database and the polling engines, as the Database processing and polling can be resource-intensive.

    Hope this helps.

Reply
  • Hi  ,
    In 2015, our Solarwinds monitoring solution used a physical server to monitor the Virtual Infrastructure running on VMware.

    Now, it has been converted to a fully virtualised environment on VMware. Set up the Affinity rule to separate the Database and Polling Engines VMs to a different host to avoid resource contention and redundancies.

    The most important thing here is the dedicated or separate SQL Server database and the polling engines, as the Database processing and polling can be resource-intensive.

    Hope this helps.

Children
No Data