Symptoms

Feature request for:

- We could separate the DB installation so we could either provide a script and/or dacpac to a SQL administrator to create the K2 database for us.
- After the initial setup of the DB, the K2 service account and/or K2 admin should have enough permissions to perform upgrades, reconfiguration and so on.
 

Diagnoses

See resolution
 

Resolution

We linked this ticket to the following TFS item: 533799 - K2 Installer: SQL Permissions: Reconfigure and Repair: Update the installer to require dbcreator permissions only when the K2 DBs does not exist

This TFS item covers the above requests, as I have the following information from the developers.

Currently we have a massive amount of legacy code that if changed is a massive load on installer architecture and testing. Permissions have been issues for a while with regards to Server roles and allowing users to create their own databases.

In a future release of K2 - after 4.7 - The installer database model will be re-written and will no longer use the scripting method we use today to create, edit and configure databases. This in turn means that permission checks and execution methods have been re-thought and implemented for this new model.

The new model will be based on the SQL DACPAC Deployment, where we let SQL control a lot of the changes.