August 23, 2022 at 3:50 am
Hi All,
I'm in need of knowing how many SQL2019 Standard license key I need in my scenario; I'm hoping someone could help so I'm compliant with Microsoft key usages. I'm not a SQL person, I'm the DB Admin but falls upon me to provide software to others.
My server speck's:
4x HP DL360 G9s, 2x processors, 16cores total, 64Gb HP RAM, WS2019 all identical for redundancy purposes (Primary, secondary, tertiary and a forth).
Scenario:
The primary would always running (PBX server), the other three are dormant unless needed if the primary is down, the secondary would be brought online until repairs are made to the primary, then I would switch back to the Primary. The same goes for the other servers but at NO given time are two servers running at the same time although all are online to keep data in sync.
All servers are a clone of the primary servers so hardware and software are 100% identical, I don't use any VM or clustering of any kind and isn't needed in our setup. All servers SQL data is kept in sync via another software in case we need to failover to another server as our disaster recovery solution.
Question:
Since only one server is live at any given time, and Microsoft allows some redundancy in their rules, do I only need One key for all servers or do will I still need to provide a separate key for each server despite having only One server in live production?
Alexander
August 23, 2022 at 7:52 am
MS knows the answer and MS can vouch for it. Best route is to contact MS
As far I can read is that if you have SA (subscription) you're allowed one active (primary) and one secondary/passive (ready to takeover). More than one passive isn't really covered
There are free dev-licenses (not meant for production)
August 23, 2022 at 3:42 pm
Hi Jo Pattyn,
Thanks for the reply, I agree MS can vouch for it and I've also read about the subscription and allowing a primary and a secondary/passive. However, that subscription is over $2000 covering only two servers, and not a one time fee which makes it costs a small fortune! It would be Far less expensive to buy 4 separate life-time/retail licenses that run about 400.00 each for my particular setup and not worry about it, would it not?
I guess I was asking if I could buy one key for all four servers as long as only one is in production at any given time like a windows keys, SQL should be the same unless MS has very different rules for that product. Calling MS is a horrible experience every time.
August 23, 2022 at 7:40 pm
You need to speak to your license vendor and or Microsoft.
Never trust what anyone says on a public forum as truth, especially when it comes to something as ultimately complex and legally binding as licensing. One false move and your up the proverbial without a paddle.
However the $400 license you speak about is a little cheap. I guess your talking the server/cal route there, well that then comes with its own interesting licensing quirks.
What are the systems running, how many users will be accessing it, is it a web client, is it externally facing.
There will eventually be a tipping point where it is cheaper to just licence per core than server and cal. Remember as you add more users and devices which access the system you need more cals, you just don’t buy the $400 server license and that’s it. You need to keep your CAL licenses in check every day also.
But seriously, licensing has its quirks and legal points which need to be addressed, speak to MSFT or your provider, they will tell you the best way to license what it is this system is purposed for.
August 23, 2022 at 8:02 pm
Hi,
All good points!
I'm purchasing by core (16) per server with 25 device cals per server, they don't face the public, they are internal and no one logs in other then two admins. however, they do connect to other servers that use the DB SQL resources known as trunk servers that process calls, only an admin is allowed direct access to the server. I have 9 trunk servers and would count as a devices so 25 cals is should be fine, usage on Cals won't change much since its the same devices connecting all the time 24/7. I just may increase to 50 just in case.
Yes, 400 is a bit cheap, I see them for about 700-800.00 SQL2019 Std plus CALs which sounds about right, we won't need to upgrade and certainly would never downgrade so no need for the ENT version which helps with the costs. It looks like I'll need to take the time to spend hours on hold with MS to get an answer directly from them. :/ Your right, I don't want any issues with key usages! thx!
August 23, 2022 at 9:14 pm
It’s not just direct access you need to count for CALS, anything which would indirectly access it would also need a CAL.
So a VOIP phone connected to trunk which connects to SQL so you need a device CAL for the phone and one for the trunk. So it can mount up quite quickly.
You don’t need to speak to MSFT directly, if you purchase your licenses via a vendor they will be best placed to answer the questions. They should know your existing agreements and what you can / cannot do.
August 24, 2022 at 1:42 am
Correct on the VoIP phones yes, but we don't provide that type of service, we provide virtual office, toll free, faxing so CALs won't apply since the DB only connects to trunk servers to process calls, 5 trunk servers would = five CALS but each trunk server has 100 SIP licenses to process calls 100 calls per server. I'm definitely going to speak with MSFT to make sure I'm compliant!
I'll keep everyone posted on what they say.
Thank you all for chiming in.
September 2, 2022 at 4:47 am
Hi all,
Well MS is of no help after a week on the phone with them tryin to get answers, different people say different things so no one is on the same page! All they do is refer you to their partners that mostly don't know the answer to something they should know if they are selling SQL, right?!
Anyways, I found a gold partner that were more then happy to assist in everyway!
My Questions:
1. Do I need to have a key to each backup server or a clone of the original as a backup regardless of it being online or not.
* YES, each instance of SQL is required to be licensed per MS agreements.
2. Is VL or SA more expensive when you only have a handful of users and a small/med business?
* YES, A contract may be less upfront but in the long run costs a lot more, kind of like leasing a car! In my case I went a retail key since my system and users basically stay the same with users, the DB grows but makes no difference.
3. What is the difference between Core and Server/Cal version and retail vs VL or SA.
* Core mode is for systems that have users they can't keep track but VERY expensive Example: 16cores = 7100.00 per server
* Server|Cal 2019 mode is for system that have few users and easily tracked, the software will support up to 24cores.
For a Standard SQL2019 server/CAL mode w/10 users = 1998.00 (retail lifetime key) You just can't upgrade or downgrade using
Standard version, you need ENT of you plan on making changes in the future but also very expensive.
4. Do both versions perform the exact same and have the same features?
* YES, no difference what so ever!
NOTE, I'm not a SQL person but received lots of vital info from the gold partner I'm going with.
If you want to see the video (supper helpful with licensing) check it out, they are exactly the same on the phone! 🙂
https://www.youtube.com/watch?v=XAVDKq4Q6h0
Thanks for all the help and hope someone finds this helpful.
September 2, 2022 at 1:39 pm
4. Do both versions perform the exact same and have the same features?
* YES, no difference what so ever!
Not true. The gap has narrowed considerably since 2016 SP2, but there are still differences in features (and as already discussed, CPU core and memory limits)
September 2, 2022 at 3:38 pm
Hello ratbak,
Yes, between versions but I'm strictly talking about the difference between 2019 server|CAL Std vs 2019 core Std.
I've already confirmed directly with two MS team members and gold partners. However, features between SQL2019 std vs SQL2019 Enterprise, Web, Datacenter version are very different.
September 2, 2022 at 5:42 pm
Yes, sorry -- right. Licenses are just licenses for a given edition.
As you suggested, I was focused on Std. vs. Enterprise. -- saw the word "Standard" and went on a tangent. Sorry.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply