You are trying to update your environment and follow current recommendations on how to manage our database (by default called Symantec_CMDB). You want to know about our posture/recommendation about hosting Symantec_CMDB database with other applications databases in the same instance in a SQL Server Cluster or is it necessary to have it just with its own instance and without other databases.
ITMS 8.7.x
Our current posture is the same as before regarding hosting our database in a SQL Server. We recommend following Microsoft best practices (see below), regardless of environment sizes.
In most cases, it is recommended to analyze how performance is improved or degraded when there are other databases in the same SQL instance and how they are fighting to use the same available server resources.
Our online documentation:
About Database Sizing for SQL Server (broadcom.com)
mentions the following:
"The CMDB SQL Server should not host additional third-party database applications because Symantec Management Platform has very high performance demands. However, additional CMDB databases can be hosted on the same SQL Server because each database has similar traffic requirements and hardware configuration needs.
You can have a single SQL instance that shares a single TempDB database, or multiple database instances can each have a dedicated TempDB database. Multiple database instances minimize risk for potential contention but require more disk arrays.
You may require the individual databases of each Notification Server computer to exist on a separate instance. They may need to be separate instances to avoid TempDB database contention."
"SQL Server Implementation Best Practices and Performance Tuning" (KB 178476)
"Creating a maintenance plan in SQL Server 2012 or later to optimize database performance" (KB 178814)
"How to gather an Estimated Execution Plan for a Stored Procedure or Function in the SQL Server Management Studio" (KB 207484)
"How to troubleshoot NSE processing issues" (KB 205352)