K2 Product Database Practices
The following governance rules are encouraged with regards to the product database within SQL Server instance for K2 blackpearl:
- Only designated administrators should be granted access to the K2 product databases
- Consider restricting the deployment of K2 databases to the same SQL instance used by K2 product
- If custom databases are needed for a given solution, they should be hosted on a different database instance or a different SQL Server than the K2 product databases
- The table structure of K2 product tables should never be modified
- Indexes and foreign keys on K2 product tables should not be modified
- Custom triggers and functions on K2 product tables are not allowed
- Custom .NET assemblies should not be added to the K2 product databases
- Stored procedures and views provided by K2 should not be modified
- New stored procedures and views on the K2 product tables should be abstracted to a new database
- The only schema within the K2 database that may be considered for read-only access is the “ServerLog” schema
- Directly inserting, updating or deleting data into K2 database tables outside of the API is not allowed
- The only exception to this rule is the K2 SmartBox-created tables
The SmartObject framework is an integral component within the K2 platform and should be considered as essential in any K2 solution. There are a number of factors to consider when planning the usage of SmartObjects and proper design and implementation are important cornerstones of a stabile solution.
Learn more about SmartObjects.
Metrics and reporting are commonly important elements of K2 solutions. The K2 platform provides some out-of-the-box reports to provide visibility into business processes.
However, it is also common to have to accommodate custom or complex reporting needs. Proper understanding of out-of-the-box functionality as well as common design techniques can help developing a reporting strategy.