Database

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

Overview

This section covers the database side of an on-premises Business Central deployment. It explains how to create application and tenant databases for single-tenant and multitenant setups with PowerShell cmdlets, and how to configure SQL Server authentication, including encryption key setup, so server instances can connect.

Further pages cover SQL Server installation choices (disk partitioning, virus scanning, TempDB, MAXDOP, full-text search, statistics), running the database on Azure SQL Database through a BACPAC export and import, and keeping database size under the limit with company deletion, retention policies and compression. A troubleshooting page covers connection failures.

Start with creating the databases, then configure authentication. Read the SQL Server installation page when planning the server. Use the size and troubleshooting pages when operating an existing deployment.

Key points

• Databases are created as application and tenant databases, using cmdlets such as New-NAVApplicationDatabase, Mount-NAVTenant and Sync-NAVTenant; after creation, publish extensions and add companies.
• Database authentication uses SQL Server authentication with an encryption key, configured on the database and the server instance, for single-tenant and multitenant deployments.
• SQL Server installation guidance covers disk partitioning, virus scanning, memory, TempDB, full-text search, MAXDOP, statistics management and high availability, for on-premises and Azure.
• Azure SQL Database deployment involves preparing the database, exporting a BACPAC, importing it to Azure, configuring the firewall and setting server instance authentication.
• Ways to reduce database size: delete unused companies, delete documents, apply retention policies, and enable data compression (CompressionType property).
• For connection problems, enable Named Pipes and TCP/IP in SQL Server Configuration Manager, allow SQL Server through Windows Firewall, and start SQL Browser Service for named instances.

Learn pages

• Configure Business Central Database Authentication: This article describes how to configure SQL Server authentication between the Dynamics Business Central instance and a database.
• Creating and altering Business Central databases: Create a new database by using the New-NAVDatabase cmdlet in the Administration Shell.
• Installation considerations for Microsoft SQL Server and Business Central: Learn about the requirements for installing and configuring Microsoft SQL Server to work with Business Central.
• Keeping Database Size Under the Limit: Learn about the best ways to reduce data stored in Business Central databases.
• Running a Business Central Database to Azure SQL Database: Learn how to deploy a Business Central database to Azure SQL Database
• Troubleshooting: SQL Server Connection Problems: Learn how to configure and troubleshoot SQL Server connections to Business Central.

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