May 18, 2017 - 08:14 AM
May 18, 2017 - 08:30 AM
I agree - and one VM, one instance has always been the way we've done it. However, when presenting the eye-watering costs for high core density Enterprise Edition to the architecture and tech teams they didn't seem overly concerned. Many of these DBs would be considered small footprint so maybe it will work. At least it is something we can test (for Standard Edition) with our existing licenses before making the decision to re-architect and upgrade.
May 18, 2017 - 08:47 AM
Yes. You can license on the vCPU assigned to the OSE unde rthe core model.
Yes. Under the Core-licensing method you can have multiple instance on a single OSE.
Yes, as long as you have SA you can deploy previous versions (see MS licensing document for the version they allow)
These are less of a licensing concern and more of an operational concern. The reason operations folks like VM as they provide a logical separate. If you are removing those benefits why would you use a VM?
A scenario come to mind...
What if a single instance on this OSE is consuming 99% of the cpu cycles? This impacts all Instances and there would quickly be a major problem.
My suggestion (and I know if is a financial barrier) is to license a small VM cluster at the physical level. You'll avoid the resistance from the technical folks and still gain a license cost compression. This way also allows you to buy perpertual license and possibly avoid the recurring SA charges...
May 18, 2017 - 12:42 PM
I'll put the option on the table along with the others. Techies are actually strongly in favour of the multi-instance approach which surprises me but they are very experienced DBAs so I'll defer to them.
May 19, 2017 - 02:53 AM