Changing Compatibility level of Symantec_cmdb
search cancel

Changing Compatibility level of Symantec_cmdb

book

Article ID: 408305

calendar_today

Updated On:

Products

IT Management Suite Client Management Suite

Issue/Introduction

You are trying to upgrade your SQL Server and make sure that the Symantec_CMDB is also set to a valid compatibility mode.

Does ITMS (IT Management Suite) supports changing the Symantec_CMDB database compatibility mode (for example from 2016 to 2022) to something newer?

Environment

ITMS 8.x.x

Resolution

Regarding this question about changing the database compatibility mode, the general guidance is that if the ITMS Support Matrix support the SQL Server version, we should be able to handle the same compatibility mode version as well.

If you are already upgraded to ITMS 8.8 version for example, Windows SQL Server 2022 is supported:

https://techdocs.broadcom.com/us/en/symantec-security-software/endpoint-security-and-management/it-management-suite/ITMS/Platform-and-OS-Support/microsoft-sql-server-v120809707-d780e8795.html

So, you should be fine to change from 2016 compatibility mode to 2022 compatibility mode (per this example's versions).
We don't recommend to go higher than the supported version for the ITMS version that you have or use a lower version neither. 

Another scenario to consider regarding changing the database compatibility mode is:

In cases where the version of Microsoft SQL Server used for the Symantec Configuration Management Database (CMDB) is upgraded, the SQL Server compatibility level for the "Symantec_CMDB" database will need to be adjusted using SQL Management Studio after SQL Server is upgraded.

As well, If you move your database to SQL Server 2019 (or higher) for example or you already run your database on SQL Server 2019 (or higher), make sure that the Compatibility level of your database is set to SQL Server 2019 (150) or higher before starting the ITMS upgrade. If you have the Compatibility level set to lower than SQL Server 2014 (120), ITMS upgrade will fail.

Also, our product has code that should tell you in the NS logs if there is an issue with the compatibility mode.
Example:

A critical error occurred:

System.Web.Services.Protocols.SoapException: Failed to configure database settings. --->

Altiris.NS.Exceptions.AeXException: Failed to configure database settings. ---> Altiris.NS.Exceptions.AeXException: SQL compatibility mode is too low for [Symantec_CMDB]: SQL Server 2012, (required: SQL Server 2022)

 

 

Note:
you can find more information about in-place Operating System Upgrades here:

In-Place Operating System Upgrades