Database Consolidation

A new installation will create a single database. The contents of the database is schematized to match the database layout of previous K2 versions. The following list presents the associated schemas:

K2HostServer

• Category
• CustomUM
• Designer
• Environment
• Eventbus
• HostServer
• Identity
• PackageDeploy
• Relationship
• Server
• ServerLog
• SmartBroker
• SmartForms
• SmartObject
• Workspace

When upgrading a pre-existing K2 installation, the existing K2 databases are not consolidated into one database. However, the following schematization and update procedures are done to streamline data storage and improve the performance of the K2 Server:

1. Creation of Synonyms
   • Synonyms will be created with the object's previous names and (dbo) schema to support binary reference.
2. Clean-up of Database objects
   1. Removal of depreciated code:
      • Text -> NVARCHAR(MAX)
      • Image -> NVARBINARY(MAX)
      • Old Style OUTER JOIN
      • Replaced sp_openxmldocument with xQuery
   2. Unicode Storage 
   3. Preparing the database for case breaking
   4. Using Scope_Identity instead of @@Identity
   5. Renaming the Indexes
   6. Making use of IF EXISTS(SELECT 1… instead of IF EXISTS(SELECT COUNT….
   7. Using Fully Qualified Object Names
   8. Renaming Tables

Dealing with Custom Database Objects

All stored K2 procedures, functions, and views have been dropped and re-created as part of the databse schematization that occurs when upgrading to K2 4.6:

1. All dbo objects have been moved to the correct schema
2. All code in stored procedures, functions, views are updated to call the schematized objects.
3. The K2 4.6 update creates synonyms for these objects – and the referenced objects must be removed from the dbo schema in order to do this successfully.

 It is possible to preserve your custom and future database objects within your K2 databases. To do this you must move your custom objects to their own schema – for example, move [dbo].[MyCaseSP] to  [CaseSchema].[MyCaseSP] before performing the upgrade. Use a simple script if you have the names of the objects you want to preserve. If you do not want to update your code to reference the schematized objects then you will need to create synonyms for them.