Manage Database Size

The size of the K2 Database can grow to be much larger to improve database management. The K2 Archive Utility enables the administrator to export the completed processes to a K2 Archive Database.

Database Access

Access to the databases is secure and two options are available when installing K2. During installation, the Database Settings dialog will prompt the installer to select either Windows Authentication or SQL Authentication.

Provided the User Account accessing SQL has the appropriate login credentials, either one of the two methods can be used. If SQL Authentication is selected, a connection string is stored in a configuration file which makes access to a database containing secure information vulnerable if the folder where the configuration file is located unsecured. Windows Integrated Authentication is more secure, as the login credentials are managed via Active Directory and user names and passwords are not exposed in plain text in a configuration file.

Installing the Database

The database can be installed either locally or remotely. To install the database remotely, the K2 Service Account must have been allocated access rights on the remote SQL Server. Refer to the Installation Account permissions for further details.

While infrastructure changes are required by K2, each environment is different and has its peculiarities which must be taken into account. Modifying the infrastructure could have unforeseen results if the changes are not appropriately understood or managed. Given the broad spectrum of underlying infrastructure utilized, it is recommended that a panel or committee with appropriate skill in each area concerned be assembled to outline the underlying infrastructure changes and gauge the impact of the required changes.