Database Files

The App Control Server database consists of five different files. Additionally, SQL Server keeps two temporary files for its operations. The following table lists all of the relevant database files:

Filegroup Name	File name	Description	Type
PRIMARY	das.mdf	Stores data that is not related to inventory or events	Data
SECONDARY	das_events.ndf	Stores event data	Data
ABINST	das_abinst.ndf	Stores inventory data	Data
ABTEMP	das_abtemp.ndf	Stores inventory indexes	Index
Log file	das_log.ldf	Stores transaction log	Log
Temp SQL data file	tempdb.mdf	Stores temporary SQL data	Temp
Temp SQL log file	tempdb.ldf	Stores temporary SQL data	Temp

As mentioned in the OER, the App Control database should be stored on direct attached storage (DAS). For larger deployments (over 10,000 endpoints), additional flash SSD storage should be used.

There are three ways to split database files, depending on desired performance, size and file type:

Layout	Endpoints	Data	Index	Log	Temp	AEFW Note 2
Standard performance	<10,000	DAS	DAS	DAS	DAS	N/A
	>=10,000	DAS	Flash	DAS	DAS	13 GB
High performance Note 4	Any Note 1	Flash	Flash	DAS Note 3	Flash	20 GB

Note:

• 1: The High-performance configuration is not required for any deployment size. However, it will provide the fastest response for App Control Server console activity. Note, however, that it will also increase total hardware cost since flash storage is still more expensive than hard disks.
• 2: AEFW represents Annual disk writes to the flash storage in bytes for single endpoint. It is used in the flash storage lifetime calculation in the next section.
• 3: Transaction Log Files should never be put on the flash storage. DAS storage usually has equal or better sequential write performance than flash, so it is not required. Also, given that flash storage usually has a limit on lifetime number of writes, it is better to store log files on less expensive DAS drives.
• 4: "High performance" mode will provide up to 30% higher performance for most server operations.