< class="prominent-subhead ">

K2 and upgrading SQL Server instance for SharePoint

This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.


You need to move SharePoint 2010 back end databases (system and content SharePoint databases) to a new SQL Server instance, moving to a newer version of SQL Server (e.g. move from SQL Server 2008 R2 to Microsoft SQL Server 2012). Upgrade of SQL Server version requires applying FP/CU for SharePoint 2010 to get support for SQL Server 2012. What will be impact for K2 in this scenario?

Before You Begin

In this scenario you need to understand the following:

1. K2 does not interact with SharePoint databases directly (neither with system nor with content databases), it only interacts with the SharePoint server itself. Hence if migration of SharePoint databases is performed correctly there should be no impact on K2 as it keeps connecting to and working with exactly the same SharePoint server of the same version.

2. In case of SharePoint 2010, for it to be able to work with SQL 2012 it is necessary to apply SP1 for SharePoint 2010 - see details in Microsoft documentation: Hardware and software requirements (SharePoint Server 2010) 

In case you update a product version that integrates with K2, you have to refer to K2 Product Compatibility, Integration and Support documentation and "K2 Product Support and Release Strategy" to make sure that this combination is supported. For K2 4.6.11 and SharePoint 2010 archived information can only be found in "K2 blackpearl 4.6 Compatibility Matrix (Archive)". There you can see that K2 4.6.11 supports SharePoint 2010 version up to SharePoint 2010 SP2 August 2015 CU.

For current versions of K2 products, all supported 3rd party products FP/CU updates are supported during the product support cycle. As stated in "K2 Product Support and Release Strategy" document.

"As long as the third-party vendor maintains backwards compatibility with the APIs and integration points K2 uses, minor releases (such as service packs, cumulative updates, or patches) of third-party products are supported."

How-to Steps

To conclude: upgrades/updates of back-end components of the products which integrates with K2 should not have any impact on K2, but upgrades to those products themselves may have an impact and it is necessary to consult with K2 documentation to establish whether an updated/upgraded version is supported.