Hi
If I understand your question correctly, you get permission errors from sql server if the new users are not dbo database role.
I think this is not necessary, if you follow these steps (applicable for navision db authentification):
1) create a sql login for the new new user
2) create this user in navision as db login
3) run tools->security->synchronize (may take a looooong time)
Navision users performing actions like uploading licenses, creating tables etc may need dbo or similar indeed.
The only Navisoon users that are required to be members of the SQL DB_Owners Role are those that will be modifying or creating tables,as they need rights to change or create the underlying SQL Objects.
Other SQL Role requirements:
Backup/Restore: SQL Backup Role or higher
Security Sync: SQL Security Admin or Higher
There may be other I can't think of right now. A general SQL rule (not just Navision) - If a user is not involved in development, they have no reason to be in the DB_Owner Role.
Comments
If I understand your question correctly, you get permission errors from sql server if the new users are not dbo database role.
I think this is not necessary, if you follow these steps (applicable for navision db authentification):
1) create a sql login for the new new user
2) create this user in navision as db login
3) run tools->security->synchronize (may take a looooong time)
Navision users performing actions like uploading licenses, creating tables etc may need dbo or similar indeed.
Regards
Thomas
Other SQL Role requirements:
Backup/Restore: SQL Backup Role or higher
Security Sync: SQL Security Admin or Higher
There may be other I can't think of right now. A general SQL rule (not just Navision) - If a user is not involved in development, they have no reason to be in the DB_Owner Role.