/
Why do users have to be explicitly assigned to licences on cloud/hosted SQL Servers?
Why do users have to be explicitly assigned to licences on cloud/hosted SQL Servers?
Question
Why do users have to be explicitly assigned to licences on cloud/hosted SQL Servers whereas on on-prem servers they can be unassigned, allowing concurrent licencing.
Answer
Users have to be explicitly assigned on cloud/hosted servers because Jiwa doesn't have permissions to look in the sys.sysprocesses table in the master database, to see which users are connected and thus no concurrent licencing.
In the next major release (post 07.02.01) we are using contained database authentication by default, so all users will have to be assigned regardless of the server being on-prem or hosted. There will be no concurrent licencing.
, multiple selections available,
Related content
End-user License Agreement
End-user License Agreement
More like this
What is the difference between Pooled and Named Jiwa licences?
What is the difference between Pooled and Named Jiwa licences?
More like this
Provisioning an Azure environment
Provisioning an Azure environment
Read with this
Transaction log grows to a large size due to uncommitted insert to SY_LicenceUsages table
Transaction log grows to a large size due to uncommitted insert to SY_LicenceUsages table
More like this
Error performing a yearly roll-over in a Azure 7.00.157 database 'Master.dbo.SysProcess .. is not supported in this version of SQL'
Error performing a yearly roll-over in a Azure 7.00.157 database 'Master.dbo.SysProcess .. is not supported in this version of SQL'
More like this