Some distributions are heading that way but there’s still some pretty massive MySQL open source based deployments out there…… and I honestly don’t think that will change much with Oracle involved. I know that’s hard to believe :)
> On Nov 6, 2016, at 8:03 PM, Ken Hohhof <[email protected]> wrote: > > What I meant was that Oracle’s acquisition of MySQL has caused many Linux > distributions and applications to switch over to MariaDB as a drop-in > replacement. > > <> > From: Af [mailto:[email protected] <mailto:[email protected]>] On > Behalf Of Josh Reynolds > Sent: Sunday, November 6, 2016 6:13 PM > To: [email protected] <mailto:[email protected]> > Subject: Re: [AFMUG] SQL Server Express Edition question > > Oracle is... Roughly 10x worse with much higher costs. > > Imagine thousands of Oracle Linux VMs running oracle databases, on IBM z/OS > PowerPC 42U servers with triple redundant hardware... I maintain a few of > those. Pricetags in the tens of millions :/ > > > On Nov 6, 2016 5:37 PM, "Ken Hohhof" <[email protected] > <mailto:[email protected]>> wrote: >> It’s Windows based commercial software. Nice try, James T. Kirk. >> >> Oh, and don’t you mean MariaDB? Is Oracle any less scary than Microsoft? >> >> <> >> From: Af [mailto:[email protected] <mailto:[email protected]>] On >> Behalf Of Josh Reynolds >> Sent: Sunday, November 6, 2016 4:05 PM >> To: [email protected] <mailto:[email protected]> >> Subject: Re: [AFMUG] SQL Server Express Edition question >> >> Extract the data and push it into mysql/Linux? :) >> >> >> On Nov 6, 2016 3:47 PM, "Ken Hohhof" <[email protected] >> <mailto:[email protected]>> wrote: >>> Does anybody understand the licensing model for this? >>> >>> I have a Windows based legacy mailserver running on Windows Server 2003 web >>> edition that needs to be updated to a newer version of the OS and to new >>> hardware. So I don’t believe any CALs are required, but even so, the price >>> for SQL Server Standard will be a showstopper at something like $3000 I >>> think? >>> >>> The limitations seem to be 1GB memory, 10GB database size (per database), >>> and 1 physical CPU. I see where the server can have more than 1GB memory, >>> but SQL will be restricted to not using more than 1GB of it. Thankfully, >>> because who would have that little memory in a server. >>> >>> But what about the 1 physical CPU. I am wanting to put this on a used >>> DL380 G7 with dual 6-core CPUs. I can’t find how the single CPU is >>> enforced. Is it >>> >>> a) Will refuse to run on a dual CPU machine >>> b) Similar to the memory limitation, will run but SQL will only use 1 CPU >>> c) Not enforced until Microsoft does an audit and forces me to pay $3000 >>> plus fines >>> >>> Oh, and don’t get me going on licensing for Windows Server 2016, that looks >>> feasless, I assume I need to go with 2012 R2.
