[Info-vax] vax vms licenses

[Kerry Main]

> -----Original Message-----
> From: Info-vax <info-vax-bounces at rbnsn.com> On Behalf Of Phillip Helbig
> undress to reply via Info-vax
> Sent: April-27-22 9:03 AM
> To: info-vax at rbnsn.com
> Cc: Phillip Helbig undress to reply <helbig at asclothestro.multivax.de>
> Subject: Re: [Info-vax] vax vms licenses
> 
> In article <t4aeqg$vk1$1 at dont-email.me>, Dave Froble <davef at tsoft-
> inc.com> writes:
> 
> > I do find it interesting that the worst doomsayers are those without
> > any relationship with VSI.  Any current customers with VSI support out
> > there have much to say about the issue?
> 
> There is an obvious selection effect here: those who are fine with the
license
> policy are fine being VSI customers.  Those who aren't, aren't.
> 
> 

Keep in mind that there are major SW licensing changes happening with other
vendors as well.

Case in point - Microsoft changing their SQL licensing to a core based model
similar to how Oracle does its licensing.

With HW vendors increasing their core counts on even small servers to be
more competitive, this typically means higher overall licensing costs.

Sample reference:
<https://redmondmag.com/articles/2019/11/08/sql-server-2019-licensing.aspx>

OpenVMS used to be core based back in the HP OpenVMS pre-V8.4 days and
moving to socket based was viewed by Customers as a major positive move.

Imho adopting either core or socket based HW licensing with all of the
variants and options is just way, way to complex these days. Most Customers
want simple licensing terms that do not need a license sales specialist to
explain exactly how many licenses are required.

Subscription models with exceptions for some Customers who require perpetual
is the way to go in the future and that appears to be the way VSI is
heading.


Regards,

Kerry Main
Kerry dot main at starkgaming dot com







-- 
This email has been checked for viruses by AVG.
https://www.avg.com