Control Compliance Suite (CCS)
When installing the MSSQL CCS Snap-in on servers that you would like CCS to scan the MSSQL databases, the Microsoft SQL client is no longer installed automatically with the CCS SQL Snap-in. The MSSQL client now has to be installed manually on each agent to collect SQL data.
The Microsoft SQL client would sometimes force a reboot of the server, and that is not something that Symantec can control or change. Because of this feature from Microsoft, Symantec has removed the MSSQL client from our install and it now has to be manually installed on each server before CCS will be able to collect SQL data.
Release : 12.5, 12.5.x
Component : CCS Agent with the SQL Snap-in required for data collection of MS SQL assets
For data collection of MS SQL databases on a server with a CCS agent, the MSSQL client needs to be installed on each agent so CCS can collect data.
From SCU 2019-2 onwards, for agent-based data collection you must manually install specific drivers depending on the version of operating system of the agent computer and corresponding versions of MS SQL Server.
For SCU 2019-2 to 2020-1 for MS SQL 2008(R2):
NOTE: SQL 2008 (R2) has been deprecated by Microsoft as of January 2021, and is no longer supported by Symantec as of CU 2021-1
For SCU 2020-1 onward:
For all other supported MSSQL databases:
Currently supported platforms and databases:
Information on the new release of OLE DB Driver for SQL Server from Microsoft: