Hardware and performance guidelines
Last updated 11 November 2020.
For the purposes of this page, a server is defined as a host machine plus a single SQL Server instance.
These values are guidelines only. They are based on our experience of typical server workload and the typical performance of the system that V8 Search XE is running on. If you are monitoring host machines with several instances and highly-active databases, you may require more performant hardware, and if you are monitoring relatively quiet servers you may require less.
Key performance requirements
A V8 Search XE installation has three components:
- a V8 base monitor, responsible for sampling, managing and interpreting the sampled data,
- the repository, a SQL Server database that holds the sampled data and V8 Search XE configuration settings,
- X numbers of V8 Services sitting between Dynamics NAV/BC Server instance and the data sampled by the V8 base monitor.
V8 Base monitor capabilities
We recommend that the V8 base monitor supports a maximum of 1 Dynamics NAV/BC produktion SQL Server.
V8 Service requirements
The specification of the V8 Service for Dynamics NAV/BC Server instance depends on wich AL Source Code and from where. We recommend allowing plenty of extra resources for expansion as you may add additional V8 base monitors as your estate grows.
Perhaps most importantly: this does not and cannot take into consideration slow networks/WAN links. The speed of V8 Search XE is limited by the communication time with the slowest V8 Service.
We recommend using high performance SSDs.
The amount of disk space required also depends on your data retention policy and whether your V8 Search XE database (data repository) uses a SIMPLE or FULL recovery model. Setting short data retention windows and using the SIMPLE recovery model will help to minimize disk space requirements.
SQL Server for the repository
We recommend using SQL Server 2017/2019 Express with Advanced Services or SQL Server 2017/2019 Standard. If you are using SQL Server Express, we recommend that you set short data retention windows (1 week for data for which you want to view trends, 3 days for troubleshooting) and monitor or profile no more than 20 Dynamics NAV/BC Server instances.