QoL-issue on DVLS-Updates when using sql logins with restriction on the

Good morning Devolutions community,

today i updated my DVLS test enviroment for my upcomung update on our production enviroment and i ran into a little quality of life (QoL) issue which i wanted to share. The update went smooth till the DVLS Console started updating the database and wanted to set the permissions on the sql logins for the webapp and scheduler. The reason for this issue is also known and it comes from my end. Due to internal security policys i am not allowed to give permissons higher the default db role "db_owner" in sql server to an app login and since the scritps for setting the least privileges tries to use some sys-views i will run into an error.

As workaround right now i always have to run the scripts for settings the permissions manually. This is no big deal, but i little bit anoying. Its also not possible to use domain credentials, because our DVLS is running on an isolated network without domain membership.

Since i have a bunch of expirence with sql server i was wondering if it wouldn`t be better to use static database roles? I whould create specific roles for the management tools, scheduler and webapp and bind the permissions on database objects onto them. Then the database admin can add the users into those roles. This would solve this issue and is also more transparent to the database admin. Maybe this will also simplify the internal update process.

I am looking forward to the feedback and let me know if further information is needed.

Cheers,

Markus