SQL Server License


We’re planning a new installation of Navion 4.02 on SQL Server. How to license SQL Server? BTW: Express edition is not an option.

Is it calculated as concurrent connections to SQL Server (no matter what programm is connecting)?

I guess, the number of CALS should be at least the no of licensed Navision session?

If the customer already has a SQL Server up and running, there is nothing else to license (provided CALS are ok)?

Is it recommended to use the SQL Server Runtime edition? As I understand, on such a server only Navision can be run (by licensing means, not technical).




First, you should take a look on the official MS Website to learn about the basics of licensing SQL Server: http://www.microsoft.com/sql/howtobuy/default.mspx

I personal recommend to buy the “Enterprise Edition”. Of course, that’s the most expensive one, but due to no limits, it’s the best edition regarding to scalability of the system.

In my opionion, the NAV Runtime licensing is a quite good option, because one could save a lot of money! The Enterprise Edition SQL Server 2005 costs 220 EUR per User. So for a 25 User Environment, you’ll have to pay 5500 EUR - that’s all! The MS price here is about 14.000 USD (~ 10.000 EUR), which is almost the double price! If you have a VPO, you’ll also get discounts.

As the SQL Runtime license is part of the NAV license, you’ll have to pay the 10% annual upgrade fee for it - but this covers all upgrades to further versions of SQL Server! As far as I known, such an license upgrade is not available with usual MS licensing!

It is true, that it’s only permitted to run a NAV db with this RT license. But that’s all a matter of argumentation: e.g. if you have a POS db on the same server, which is interfacing with the NAV db, well, the POS db is actually part of the NAV system … to you HAVE to run it on this server [6]



Purchase the SQL edition that meets your needs. Purchase Enterprise Edition only if you require the capacity or features. It makes no sense to pay for features and capacity you will not use.

You can purchase Software Assurance that allows for version upgrades.

With the runtime license you are restricted to running only the Navision database on the server. No other databases can be run there. This includes any databases that communicate with Navision, even these must be on different servers.

I don’t fully agree, sorry …

Yes, you have to pick the edition which meets your needs, but I strongly recommend to make a good forecast how the system will be in future, especially how the transaction- and data-volume will increase, how important reporting will be, and so on … You have to have in mind, that there is option available to upgrade from a Standard to an Enterprise Edition, in this case you would have to re-buy the liceses - and that’s even more expensive. So, when picking the right edition “think” into the future!

When it’s about the databses you can run on runtime: So, what’s about system related databses? E.g. databases which are used by NAV maintenance tools which have to be on the same server? These db’s are actually equal to msdb or master. What about db which contain historical NAV data, apart from the productive db, which are linked with the “real” NAV db for integrated reporting? What about db which temporary contain EDI data of external systems, e.g. orders, which are imported into NAV? There are plenty of reasons, where you have to have multiple db on the same server, e.g. to make various kinds of backups, security settings, performance, and so on.

IMO it’s absolutely not acceptable to NOT permit running those dbs on one server, because they’re all part of ONE AND THE SAME NAV SYSTEM. We have negotiated this with MS and they agreed on that point.

I have to admit, that running a POS db on the server was a bad example, as here the primary usage is not NAV related … so, as stated: it’s a matter of argumentation: ask you local MS/MBS partner!

Just one remark to the “Software Assurance” thing:

As far as I know, - please correct me, if I err -, is an option to get upgrades of an MS product. But this means, if you have bought a “Standard Edition” you will get only upgrades for STD - because “Enterprise Edition” is considered a separate product! “Software Assurance” does not allow switching between products - or in our case editions, so no upgrade from STD to EE … Right? Wrong?

That is correct. Software Assurance maintains the current product only. It allows upgrades to new releases of the same product.

Purchase the SQL edition that meets your needs. Purchase Enterprise Edition only if you require the capacity or features. It makes no sense to pay for features and capacity you will not use

I never said don’t buy Enterprise. I said buy the edition that meets your needs. This should include a reasonable look into the future, but over selling can quickly kill an entry-level deal. Selling Entrprise Edition to a client because they might need it in 2-3 years is like a car dealer in Florida selling you snow tires because you might move to Maine.

The cost difference between the versions is sizable and would probably buy the server hardware in many startup systems. It also becomes a very visible budget item subject to closer review. A system that grows large enough to require a move to Enterprise would also probably require a hardware upgrade at that time.

With SQL 2000 supporting a 4-way system with HT processors (or dual-core) required the Enterprise Edition. Under SQL 2005, this same system can be supported on Standard Edition. SQL 2005 also supports more memory than the prior version.

On the subject of run-time licenses, my experience tells me the Microsoft look more at the applications than the number of databases. This means that you would probably be okay running multiple Navision databases (other license considerations aside) but could not (for example) put your CRM database on that server.

The base SQL databases (master, msdb, etc.) are part of the core system and are covered by the license.

My experience with Microsoft on license issues is that they are open to intepretation. You can pose the same question to 3 people and get 3 different answers. I have implemented configurations for clients (with Microsoft blessing) and then with the next client be told by MS that I could not do the same thing.

Time to do some real work…