topic hubPlatform, DevOps & Performanceofficial - Microsoftreviewed - checked by Opus

Configuring Business Central database

Configuring the Business Central database for on-premises deployments: SQL Server installation considerations, compatibility level, performance tuning, index management, table partitioning, data compression, and read scale-out. It answers setup and tuning questions about the SQL database behind Business Central.

Path: Business Central on-premises > Administration > Configuring Business Central database · tier official · system platform · narrative reviewed (checked by Opus)

Overview

This section covers how to prepare and tune the SQL Server or Azure SQL database that Business Central uses on-premises. It starts with installation considerations such as disk partitioning, virus scanning, memory, TempDB, full-text search, MAXDOP settings, statistics management and high availability, for both on-premises and Azure deployments.

The remaining pages cover tuning. One sets the SQL compatibility level to match the server version. The performance guide covers data access, table keys, bulk inserts, queries and monitoring tools. Other pages cover managing index usage per company, using table partitioning and data compression, and configuring read scale-out with read-only replicas.

A good starting point is the installation considerations page, then the compatibility level page. The performance guide is the overview for tuning, and the other pages go deeper on single techniques.

Key points

  • Installation considerations cover disk partitioning, virus scanning, memory, TempDB, full-text search, MAXDOP, statistics and high availability.
  • Set the database compatibility level to match the server: 140 for SQL Server 2017, 130 for SQL Server 2016, to enable the latest optimization features.
  • Index usage can be managed per company: view usage statistics and storage size, and turn indexes on or off, including off for all companies.
  • Disabling nonessential indexes can improve write performance and reduce storage costs. Unique indexes and primary keys cannot be disabled.
  • Table partitioning and data compression are supported for on-premises databases to improve manageability, query performance and storage use. The CompressionType property is involved.
  • Read scale-out uses read-only replicas. Enabling it needs support checks on Azure SQL Database or SQL Server and server instance configuration.
  • The performance guide covers compatibility level, data access, table keys, bulk inserts, query hints and monitoring tools.

Learn pages

Videos and posts

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

Business Central pages and reports

The pages, reports and queries this hub’s Learn pages name (ms.search.form, API reference), joined to the code by exact object id (data/index/docs-objects.json); a page shows the table it runs on.

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 6 Learn pages