Carbon Black App Control SQL Server Configuration v8.6

[#1]

Document Version: 1.0

Date: February, 2021

Carbon Black App Control uses a single SQL database named “das”. This database will be created on the SQL server once you install the Carbon Black App Control Server.

This document describes some of SQL best practices as well as pre- and post-installation tasks that are necessary to ensure proper database operation.

Most of the database queries described in this document require sysadmin privileges on the SQL Server.

Important: This document is a supplement to the Carbon Black App Control Operating Environment Requirements document for your release, called the “OER” through most of this document. Information in the OER is necessary for successful completion of the tasks in this document, so you should have both documents with you when performing the tasks described here.

Note: This document applies to all 8.6.x versions.

See the Comments below for changes in this version.

[BFortin]

Change log for Carbon Black App Control SQL Server Configuration v8.6.pdf (changes since the 8.5.4 version):

1. Updated Frontmatter version Copyright date.
2. On page 4, under Choosing Proper Hardware for the SQL Server, removed Windows Server 2008 R2 from the second bullet.  It is no longer supported.
3. On page 4, under Choosing Proper Hardware for App Control Server, replaced Windows Server 2008 R2 with Windows Server 2012 R2.  Windows Server 2008 R2 is no longer supported.
4. Minor editing and formatting changes were made that had no impact on content meaning.

[hinsor]

Where do you update the server name of the SQL server? For example if the server changed names and the das database has been cloned to the new server. Old server is now powered off. App Protection wont even give a login prompt to get to system configuration. How do you tell it to use the new server?