Symptoms
Issue:
The client has recently gone through the DB merge tool to consolidate our Live environment's K2 DBs into the newer unified DB model. For a variety of reasons, the effort involved taking the live DBs to another environment, running the K2 DB merge tool, and finally taking the result back to the live environment. Everything went smoothly for the most part, except the "SCSSOKey" in SQL.
Once we got to the part where the live K2 servers started up with the new DB, we got some errors related to the SCSSOKey. My understanding is that if / when a K2 DB is restored to a new DB, the SQL encryption certificates need to be reconfigured. We did so by using a script that we used a few years back for a another DB restore effort (see attached script).
Diagnoses
Diagnosis:
I have confirmed with a senior colleague that this should not be change as it is not recommended to make a change to the script and as this also has not been tested extensively we recommend to leave the EXPIRY_DATE as is.
Resolution
Resolution:
The clients questions were answered to the clients satisfaction. " it is not recommended to make a change to the script and as this also has not been tested extensively we recommend to leave the EXPIRY_DATE as is"
