If you "change" to the license every time you connect it's not counted.
If the license is installed in the instance or the database it's in the File->Database->Information->Sessions. The value there is the sum of the number of NAS instances and the number of users; there are normally 1000 NAS users, there are often 20 normal users so the sum is 1020.
The license can be installed into a database so it'll only count the number of users attached to that database not the entire SQL instance.
The NAS (Navision Application Server) needs a session to connect to the database but they are priced differently from normal GUI client users so they are put into two distinct boxes on the license itself.
You cannot connect to the database with a GUI client if all the GUI client licenses have been used, even if there are available NAS client licenses.
You cannot connect to the database with a NAS client if all the NAS client licenses have been used, even if there are available GUI client licenses.
Two distinct user counts for the two types of client (fin.exe and nas.exe) that can connect to the DB.
The NAS client runs as a windows service and does not display anything on the screen.
How many users are allowed to work simultaniously in Developer License?
Why do you need to know this?
The ONLY valid reason for needing many log ins with a developer license are for performance load testing. For this you can apply to Microsoft for a special testing license for your customers specific application. Please read on MSDN and Partner Source for more information.
The ONLY valid reason for needing many log ins with a developer license are for performance load testing.
Actually it's a lot more convenient to install the dev license at the instance level on the dev machine than it is to install a separate copy to every dev database or worse yet have to 'change' to it every single session.
However, considering Microsoft's attitude an SQL script to update every database with a new copy of the dev license is probably easier than getting them to be reasonable.
Comments
If the license is installed in the instance or the database it's in the File->Database->Information->Sessions. The value there is the sum of the number of NAS instances and the number of users; there are normally 1000 NAS users, there are often 20 normal users so the sum is 1020.
The license can be installed into a database so it'll only count the number of users attached to that database not the entire SQL instance.
If you need more users ask Microsoft.
TVision Technology Ltd
I got your point.
One thing unclear is 'Difference between NAS user and Normal User'.
Can you please describe?
Ahmedabad, Gujarat, India
E Mail : ravi.thakkar@hotmail.com
You cannot connect to the database with a GUI client if all the GUI client licenses have been used, even if there are available NAS client licenses.
You cannot connect to the database with a NAS client if all the NAS client licenses have been used, even if there are available GUI client licenses.
Two distinct user counts for the two types of client (fin.exe and nas.exe) that can connect to the DB.
The NAS client runs as a windows service and does not display anything on the screen.
TVision Technology Ltd
Why do you need to know this?
The ONLY valid reason for needing many log ins with a developer license are for performance load testing. For this you can apply to Microsoft for a special testing license for your customers specific application. Please read on MSDN and Partner Source for more information.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Actually it's a lot more convenient to install the dev license at the instance level on the dev machine than it is to install a separate copy to every dev database or worse yet have to 'change' to it every single session.
However, considering Microsoft's attitude an SQL script to update every database with a new copy of the dev license is probably easier than getting them to be reasonable.
TVision Technology Ltd