Hello,

I can confirm this is a bug and i will log it to be fixed for the next release. Can you confirm if you are also noticing the name same for users?

Kind Regards

Trevor Robinson

Yes exactly, same issue for database users.
As a hosting provider one can consider it to be solved immediately either drilling some manual code into DB or somewhere you better know because in other case it looks awkward to restrict your user while you are actually not able to do that.  So request you to resolved this issue on temporary basis and later it can be overwrite with the next releasing script.
Shall be thankful

Hello,

Please backup you SQL database and run the following code in SQL Management Studio:

IF NOT EXISTS (SELECT * FROM [dbo].[Quotas] WHERE [QuotaID] = '711' AND [ItemTypeID] = '73')
BEGIN
UPDATE [dbo].[Quotas] SET [ItemTypeID] = '73' WHERE QuotaID = '711' AND [QuotaName] = N'MsSQL2017.Databases'
UPDATE [dbo].[Quotas] SET [ItemTypeID] = '74' WHERE QuotaID = '712' AND [QuotaName] = N'MsSQL2017.Users'
END
GO

This should then correct the ItemTypeID for the MsSQL 2017.

Kind Regards,

Trevor

Issue Solved. Great Help. Thanks