Issue
Why is the 'k2_schema_owner' SQL account created by the K2 Installer and why is it needed?
Why can this SQL Account not be modified in any way?
Additional Information
When K2 is installed, its hardcoded to create a principal k2_schema_owner and only authorize that principal for the schema. The 'k2_schema_owner' SQL account is required and can cause upgrades to fail if it is modified in any way.
The installation of K2 fails because it expects the owner of the schema in the K2 database to be k2_schema_owner since it a value the installer assigns and expects to be there. This is currently how the product functions, and it is also a best practice for SQL security to have a loginless user own the schema. If this is changed, it is not only not supported, but it also compromises on security practices.
Note
- Any changes made to this 'k2_schema_owner' SQL account is not allowed and it would place an environment in an unsupported state.
- Please also note that assigning a different account as the Principle on a K2 database Schema is also not allowed in with the K2 product.
The below SQL Query will confirm if the (k2_schema_owner) still exists on the database:
SELECT * FROM sys.database_principals WHERE [name] = N'k2_schema_owner'
Additionally, please take of the following considerations:
https://help.nintex.com/en-US/k2five/devref/5.5/default.htm#Reference/DB/Database.html
