Symantec_CMDB database installing to wrong drive on SQL server

book

Article ID: 169787

calendar_today

Updated On:

Products

Management Platform (Formerly known as Notification Server)

Issue/Introduction

During a fresh install of ITMS 8, it was noticed that the Symantec_CMDB database is installing to wrong drive on SQL server.

The defaults are set in SQL management studio for databases to reside on E:\Data.
Instead the install is going to E:\MSSQL\...\Data\

 

Environment

ITMS 8.0, 8.1

Resolution

This issue has been reported to the Symantec Development team. Changes has been done and introduced under ITMS 8.5 version (currently targeted for first quarter of 2018). It was added code that will detect during DB creation default DB and log paths for SQL versions starting with 2012.
 

The following is provided as reference on how Symantec Installation Manager (SIM) interact with SQL Server during a database creation and possible ways to address this concern:

  1. SIM doesn’t respect pre-defined default path of DB in SQL Server settings and always creates ‘Symantec_CMDB” database using SQL Server installdir.
  2. Custom location of “Symantec_CMDB” are respected by SIM in case if you are off-box upgrading, etc via option “Use existing Database” option in SIM before ITMS install/upgrade. As well, this case can be used not only for off-box upgrades, but for clean installs as well, where exact location of database needs to be defined. Just create an empty database within required location and select through corresponding option.
  3. As workaround customer can change location of ‘Symantec_CMDB’ via detach/attach or backup/restore via SQL Management studio per required SQL Instance.

Attachments