If you want to fail an IT Audit, that is a good strategy. Technically you are not blocked... but license compliance is another matter.
Microsoft doesn't care about what login is used, they care about users connecting. If you have a warehouse user on a scanner that connects to SQL through a ScanForce / ScanCo service, even without a Sage license being used, that is a SQL connection that M$ wants to be paid for. Non-Sage user who uses Excel to pull sales / inventory data from SQL: another SQL license. Sage users connect directly to SQL when printing, so one license per Sage user is a base minimum... I can't really say whether different humans on different shifts need to be counted individually (where Sage licenses by concurrent connection, Microsoft licensing rules are much more complicated, to the point I simply don't advise clients on such matters, and tell them to consult with a SQL licensing expert).
And yes, as Phil mentions, per core licensing becomes cheaper at some point. I remember @Steve Iwanowski mentioning the threshold being around 30 users, but my memory may be incorrect on that... and again, I am not an expert in M$ licensing at all.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------
Original Message:
Sent: 02-07-2024 17:51
From: Doug Higgs
Subject: When using Sage 100 Premium - How many SQL user licenses do you see customers buying?
I believe I remember @Carmen Cruz mentioning you only need 2 or 3 SQL licenses.... one for mas-user, one for mas_reports and maybe one other. I could be hallucinating again.
------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles
------------------------------