dbhiggi - Tuesday, October 13, 2009 11:02 AM:
As I understand it, SQL is sold in "editions" that come with various numbers of CALs, or one can purchase perprocessor licensing, and the server software is available for purchase separately.
What are the SQL licensing architecture requirements to support Innovator? Must I license SQL to match my Innovator users?
Thanks,
Dave
Anonymous - Tuesday, October 13, 2009 6:40 PM:
-Chris
johan.wahlstrom.tobii - Tuesday, October 20, 2009 5:23 AM:
So, in theory there would only be one license taken up for general data access.
www.microsoft.com/.../Special-Considerations.aspx
If working with named users each one requires one SQL CAL regardless on the access method.
If using SQL for anonymous users (ie public website) you dont need CALS.
Its pretty bad that ARAS suggests otherwise, beeing a Microsoft Gold Partner they should know.
Johan
PeterSchroer - Thursday, April 5, 2012 8:04 AM:
Microsoft documentation is very clear on the licensing of SQL Server behind a web application. The customer is required to purchase sufficient CALs (client licenses) equal to the number of named users, not the one (1) user which is the web server to database connection proxy. Aras has never suggested otherwise.
Typical PLM projects grow over time, as product data and processes grow to replace more and more homegrown and manual based systems. Because of this, the Aras recommendation is to purchase a SQL Server license according to the CPU's on the database server, instead of the number of users. The administrative costs of maintaining the number of users (which goes up and down over time), and constantly changing the CALS is not worth the effort. PLM is useful when it has a broad impact on the organization. If you are using a Database CAL license scheme and running PLM software that charges per user, you will be faced each week with the decision; do I let this Supplier/Engineer/Employee have a logon to PLM directly, or do I put the data into Excel and email to them, even though this creates more un-controlled sources of data. I strongly recommend the per CPU database licensing and the Aras Subscription model with annual true-ups... stop counting users. Together these gives the flexibility to have a fixed budget cost for the year, but allow the PLM user community to grow as best suits the business. No license administration during the year.
--peter.
