License issue

ta5

Hi
How to license SQL Server correctly for Navision concerning users? Is the number of SQL Cals the number of licensed concurrent Navision users or is it the number of installed Navision clients?
Thanks in advance
Thomas

Shedman

That depends on your SQL license type. You can have Per Seat (processor) license, per user license, per workstation license, BRL license. Your choice all depends on the no. of users etc.

If you just need it for NAV, I would recommend looking into BRL licensing.

Also NAV license is for concurrent users, whereas SQL uses named users.

bbrown

The only SQL licensing method that is "named users" is SQL RunTime. SQL licensing is completely independent of the NAV license. Each user much have a valid SQL client access license. There are 4 basic ways to license SQL: RunTime, Processor, Server + User CAL, Server + Device CAL.

RunTime

This is available only thru an application (NAV) vendor and is tied to that application. The server on which this is installed can only be used for that application and its dataabase. There are some exceptions for associated products. This license is by named users. That means fi you define 25 users in SQL logins, then you must have 25 runtime licenses.

Processor

Processor licensing allows for an unlimited number of users or devices to connect to the SQL server. You must purchase 1 processor license for each processor socket on the server. You must also license the operating system in the same manner.

Server + User CAL

This is actually two different licenses. While you will find combo packages that wil contain a server license and a set number of CALs, you can also purchase just a server license or just CALs. You must have a server license for each of your SQL instances. There are some special rules for Enterprise. Next each user must have a valid user CAL. This is not a named user. It is a license issues to a person.

Server + Device CAL

This is the same as above, except the CALs are issued to specific computers (devices)

David_Singleton

Thanks bbrown, that's a very concise over view. =D>

ta5

Thanks for the overview.
But I must confess, I still don't get the clue for the following example: :oops:
100 Navision Users License, Navision is installed on 200 machines. How to license a in a "Server + User CAL" scenario?

Btw: I have read the rules for runtime license and found it very stringent regarding the extenability of objects an more users. Do you share this opinion?

Thanks in advance

Thomas

bbrown

You need a User CAL for each of your employees that will be accessing SQL Server. User CALs are issued to an actual person. They are not related to the number of computers, the NAV user count, or user in SQL. Let's say you have an employee that somtimes works in their office, other times may be down on the production floor (at a different computer), other times may be traveling and using a laptop via terminal services, and sometimes accessing the system from their home PC. This person still only requires 1 user CAL. Even if they are opening multiple concurrent sessions to SQL and using different logins.

A situation where device licensing may make more sense is where your employees are sharing computers. Let say you have 150 employees that work in 3 shifts of 50 each. You only have 50 computers. Using Device CALs you would only need 50, but using User CALs you would need 150.

A few other notes

If you cannot control the number of connections, to your SQL box, you must use processor licensing. An example would be exposing your system to the public internet. Building a company website that access NAV thru webservices (or NAS) is an example of this.

bbrown

ta5 wrote:

...Btw: I have read the rules for runtime license and found it very stringent regarding the extenability of objects an more users. Do you share this opinion?...

Thomas

I agree with this observation. I've never been a big fan of the runtime license. Not to say it doesn't have its place.

ta5

Thanks bbrown
So just to be sure. If there is an installation with 100 Navision licenses for 200 different users (so only 50% of the users can work at the same time in Navision) the right choice is to license 200 SQL CALs. Is this correct?

Thanks
thomas

bbrown

ta5 wrote:

Thanks bbrown
So just to be sure. If there is an installation with 100 Navision licenses for 200 different users (so only 50% of the users can work at the same time in Navision) the right choice is to license 200 SQL CALs. Is this correct?

Thanks
thomas

Under User CALs that would be correct. However, if they shared computers (you only have 100 computers) then you could go with 100 device CALs.

Remember that you need a CAL for any and all persons that will be accessing SQL Server. Not just NAV users. So that "IT manager" that pops in and out of SSMS needs a CAL. So does the "power user" that's accessing the database with Crystal Reports.

ta5

Thanks a ton!
Regarding Runtime-Licensing, I guess the only argument for this type is the cost, isnt't it?

davmac1

I thought you could also do a runtime processor license. Then it makes sense if you plan to renew your maintenance contract every year, because you get your SQL Server upgrades included. Since 2008 SQL Server is 64 bit (except for the development version), you will get a good price and a usable version.
I believe they offer both standard and enterprise versions with NAV.

bbrown

davmac1 wrote:

I thought you could also do a runtime processor license. Then it makes sense if you plan to renew your maintenance contract every year, because you get your SQL Server upgrades included. Since 2008 SQL Server is 64 bit (except for the development version), you will get a good price and a usable version.
I believe they offer both standard and enterprise versions with NAV.

RunTime is a "named user" license. Not a "per processor" license.

bbrown

davmac1 wrote:

I thought you could also do a runtime processor license. Then it makes sense if you plan to renew your maintenance contract every year, because you get your SQL Server upgrades included. Since 2008 SQL Server is 64 bit (except for the development version), you will get a good price and a usable version.
I believe they offer both standard and enterprise versions with NAV.

But yes, you can cover it with your NAV maintenance contract. But you can also put Software Assurance on full version SQL purchase thru a licensing agreement.

bbrown

There is no right or wrong answer to choosing a licensing method. You need to review the options and pick the best approach for your requirements and budget. For smaller system that don't see multiple servers or applications, a runtime may be a valid choice.

colingl

With the SQL 2008 runtime edition, I understand the named licences, but what is to stop
me creating a database for another application (not associated to NAV) and connecting users to that.

bbrown

colingl wrote:

With the SQL 2008 runtime edition, I understand the named licences, but what is to stop
me creating a database for another application (not associated to NAV) and connecting users to that.

Because you would be in violation of your license agreement. License agreements are not about technical limitations. They are a legal agreement.

David_Singleton

colingl wrote:

With the SQL 2008 runtime edition, I understand the named licences, but what is to stop
me creating a database for another application (not associated to NAV) and connecting users to that.

The same thing that stops you going into a bank with a shotgun and telling the teller to put all the money in a big bag.

DenSter

colingl wrote:

With the SQL 2008 runtime edition, I understand the named licences, but what is to stop
me creating a database for another application (not associated to NAV) and connecting users to that.

Honour, Integrity, Not wanting to be a criminal, you know, petty things like that

colingl

colingl wrote:

With the SQL 2008 runtime edition, I understand the named licences, but what is to stop
me creating a database for another application (not associated to NAV) and connecting users to that.

bbrown wrote:

Because you would be in violation of your license agreement. License agreements are not about technical limitations. They are a legal agreement.

DenSter wrote:

Honour, Integrity, Not wanting to be a criminal, you know, petty things like that

Ok so it's a trust licence.

David Singleton wrote:

The same thing that stops you going into a bank with a shotgun and telling the teller to put all the money in a big bag.

How do you know I haven't tried that before.

DenSter

colingl wrote:

How do you know I haven't tried that before.

Good point.... if you have then it makes perfect sense that you'd want to use software without a license much less violent too