{"title":"Installation considerations for Microsoft SQL Server and Business Central","url":"https://jonas-paprotka.de/docs/dev-itpro/deployment/installation-considerations-for-microsoft-sql-server/","by":"JOP-AL","license":"Copyright (c) Microsoft Corporation. CC BY 4.0, https://creativecommons.org/licenses/by/4.0/; code samples MIT. From https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/deployment/installation-considerations-for-microsoft-sql-server, MicrosoftDocs/dynamics365smb-devitpro-pb at 828b6ee (2026-11-19). Changed: includes filled in, links to this site, and for agents shortened without dropping a fact.","credit":"Microsoft Corporation, CC BY 4.0","origin":"https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/deployment/installation-considerations-for-microsoft-sql-server","source":{"name":"Business Central developer and IT pro docs","repo":"https://github.com/MicrosoftDocs/dynamics365smb-devitpro-pb","commit":"828b6ee72fcd75755627cd6011f3d20899217ab2","date":"2026-11-19"},"checked":"2026-11-19","description":"Learn about the requirements for installing and configuring Microsoft SQL Server to work with Business Central.","date":"2025-03-12","meta":{"topic":"article"},"outline":[{"level":1,"title":"Installation considerations for Microsoft SQL Server and Business Central","slug":"installation-considerations-for-microsoft-sql-server-and-business-central","at":0,"chars":11028},{"level":2,"title":"Deploy Business Central to Microsoft SQL Server","slug":"deploy-business-central-to-microsoft-sql-server","at":408,"chars":8452},{"level":3,"title":"Storage","slug":"storage","at":459,"chars":300},{"level":3,"title":"Virus scanning","slug":"virus-scanning","at":759,"chars":203},{"level":3,"title":"Memory","slug":"memory","at":962,"chars":184},{"level":3,"title":"SQL Server components","slug":"sql-server-components","at":1146,"chars":212},{"level":3,"title":"Setup options for Microsoft SQL Server","slug":"setup-options-for-microsoft-sql-server","at":1358,"chars":4189},{"level":4,"title":"Full-text and semantic extractions for search","slug":"full-text-and-semantic-extractions-for-search","at":1562,"chars":539},{"level":4,"title":"TempDB database configuration","slug":"tempdb-database-configuration","at":2101,"chars":407},{"level":4,"title":"Data file and log file configuration","slug":"data-file-and-log-file-configuration","at":2508,"chars":540},{"level":4,"title":"Max degree of parallelism (MAXDOP)","slug":"max-degree-of-parallelism-maxdop","at":3048,"chars":1202},{"level":4,"title":"Instance configuration","slug":"instance-configuration","at":4250,"chars":624},{"level":4,"title":"Use high availability setups","slug":"use-high-availability-setups","at":4874,"chars":673},{"level":3,"title":"Database engine service","slug":"database-engine-service","at":5547,"chars":1097},{"level":4,"title":"Startup options","slug":"startup-options","at":5704,"chars":391},{"level":4,"title":"Service account","slug":"service-account","at":6095,"chars":549},{"level":3,"title":"Database configurations","slug":"database-configurations","at":6644,"chars":2119},{"level":4,"title":"Statistics","slug":"statistics","at":6878,"chars":1261},{"level":4,"title":"Index fragmentation","slug":"index-fragmentation","at":8139,"chars":343},{"level":4,"title":"Other database options","slug":"other-database-options","at":8482,"chars":281},{"level":3,"title":"Backup","slug":"backup","at":8763,"chars":97},{"level":2,"title":"Deploy Business Central to Microsoft Azure SQL Database","slug":"deploy-business-central-to-microsoft-azure-sql-database","at":8860,"chars":806},{"level":2,"title":"Data encryption between Business Central Server and SQL Server","slug":"data-encryption-between-business-central-server-and-sql-server","at":9666,"chars":321},{"level":2,"title":"Integrate directly on SQL Server objects","slug":"integrate-directly-on-sql-server-objects","at":9987,"chars":897},{"level":2,"title":"Related information","slug":"related-information","at":10884,"chars":144}],"text":"# Installation considerations for Microsoft SQL Server and Business Central\nThis article describes the requirements for installing and configuring Microsoft SQL Server to work with Business Central.\nBusiness Central can run on Microsoft SQL Server and Microsoft Azure SQL Database. For a list of supported editions of SQL Server, refer to SQL Server Requirements<system-requirement-business-central#SQLReq>.\n## Deploy Business Central to Microsoft SQL Server\n### Storage\nUse different disks or partitions for:\n Windows operating system\n Data files for system databases\n Log files for system and user databases\n Data and log files for the TempDB database\nFor optimal read/write performance, format disks used for SQL Server data files with a 64-KB block size.\n### Virus scanning\nUse antivirus software to protect computers running Microsoft SQL Server. See Configure antivirus software to work with SQL Server<https://aka.ms/chooseantivirussoftwareforsqlserver>.\n### Memory\nMaximize available memory on the server for optimal read performance, based on the SQL Server version and edition. Refer to the SQL Server documentation for maximum values.\n### SQL Server components\nWhen you install Microsoft SQL Server for use with Business Central, install at least these components:\n Database Engine Services\n Client Tools Connectivity\n Management Tools - Complete\n### Setup options for Microsoft SQL Server\nWhen you're running Microsoft SQL Server Setup, you must provide additional information. Your responses can affect how you use SQL Server with Business Central.\n#### Full-text and semantic extractions for search\n> APPLIES TO: Business Central 2024 release wave 2, version 25, and later.\nFull-text and Semantic Extractions for Search must be installed on the SQL Server instance. Learn how to check whether this feature is installed and install it at https://learn.microsoft.com/sql/relational-databases/search/install-and-configure-semantic-search.\nBusiness Central uses the full-text feature to support the modern search capability on fields in list pages. See /ui-enter-criteria-filters#searching.\n#### TempDB database configuration\nFor servers with fewer than eight cores, create as many TempDB data files as the number of cores. For servers with more than eight cores, start with eight data files and increment by four files at a time, if needed.\nMake sure that all data files for the TempDB database are of the same size.\nConsider placing TempDB data and log files on a local SSD if using SAN storage.\n#### Data file and log file configuration\nAutogrowth of the database or transaction log files in production can degrade performance because transactions must queue up and wait for SQL Server to grow the file before it can begin to process transactions again. This behavior can create bottlenecks. Grow data and log files during off-peak periods by 10% to 25% of their current size. We don't recommend disabling autogrow. In an emergency, it's better to have SQL Server autogrow files than run out of disk space and bring the database down.\n#### Max degree of parallelism (MAXDOP)\nThe SQL queries generated by the Business Central Server are of OLTP (Online Transaction Processing) type, including many small transactions. We recommend running Business Central with MAXDOP set to the value 1 as a starting point. Depending on the number of cores on your database server, you can increase this number. It isn't recommended to set MAXDOP to 0, because one query might use all resources on the databases, lowering availability for other queries.\nOn SQL Server 2016 and later, MAXDOP can be set at the database level by changing a database scoped configuration.\nBoth advanced server configuration options and database scoped configurations can be set by using SQL Server Management Studio. See https://learn.microsoft.com/sql/database-engine/configure-windows/configure-the-max-degree-of-parallelism-server-configuration-option.\n> NOTE\n> If you're running SQL Server Enterprise Edition, index maintenance can be done in parallel. If you run maintenance jobs during off-peak hours, you might want to set MAXDOP back to 0 while running these jobs. On SQL Server 2016 and later, it's possible to set MAXDOP directly in the Rebuild Index Task wizard.\n#### Instance configuration\nIf you plan to install the Business Central Demo database and want Business Central Setup to use an already installed version of SQL Server (and not install SQL Server Express), create a SQL Server instance named BCDEMO before you run Setup. Otherwise, Setup installs SQL Server Express automatically even if there's a valid version of SQL Server already on your computer. If you don't plan to install the Demo database, or have no objection to using SQL Server Express, you're free to use the default instance and Instance ID on the Instance Configuration page, or to specify any instance name.\n#### Use high availability setups\n> APPLIES TO: Business Central 2025 release wave 1 (v26) and later.\nThe SQL Server Multi-Subnet Clustering feature enables faster failover for all Availability Groups (AGs) or Failover Cluster Instances (FCIs) in versions from 2012 onwards, significantly reducing failover time for single and multi-subnet Always On topologies.\nWith the server setting EnableSqlMultiSubnetFailover set to true, MultiSubnetFailover gets enabled on the connections from the server to the database.\nLearn more about Multi-Subnet Clustering in https://learn.microsoft.com/sql/sql-server/failover-clusters/windows/sql-server-multi-subnet-clustering-sql-server.\n### Database engine service\nA separate Windows service runs each SQL Server instance. The following two things are important to configure for these services\n#### Startup options\nEnable trace flags 1117 and 1118 as startup options. These trace flags are incorporated into the default settings. Startup options can be set by using SQL Server Configuration Manager. See SQL Server Configuration Manager: Configure server startup options<https://learn.microsoft.com/sql/database-engine/configure-windows/scm-services-configure-server-startup-options>.\n#### Service account\nWe recommend using dedicated domain user accounts for the Windows services running your Business Central Server instances and your SQL Server instances instead of a Local System account or the Network Service account.\nThe Business Central Server account must have privileges on the SQL Server instances and on Business Central databases. See Provisioning the Server Service Account<provision-server-account>.\nConsider adding the service account for the SQL Server engine to the Perform Volume Maintenance Tasks security policy.\n### Database configurations\nAfter Business Central is installed, it's important to check a few settings on the Business Central databases. This task is especially important for databases upgraded from previous versions of SQL Server.\n#### Statistics\nSet the AUTO_CREATE_STATISTICS and AUTO_UPDATE_STATISTICS options on Business Central databases to ON (the default setting). SQL Server uses a threshold that adjusts according to the number of rows in the table. With this change, statistics on large tables are updated more often. See https://learn.microsoft.com/sql/relational-databases/statistics/statistics#statistics-options.\nEven with AUTO_UPDATE_STATISTICS on, we recommend running a periodic SQL Agent job to update statistics because AUTO_UPDATE_STATISTICS is triggered according to the row thresholds. On large tables with tens of millions of records (such as Value Entry, Item Ledger Entry, and G/L Entry), a small percentage of data in a given statistic such as [Entry No.] can change and have a material effect on the overall data distribution in that statistic. This behavior can cause inefficient query plans, resulting in degraded query performance until any threshold is reached. We recommend using the T-SQL procedure \"sp_updatestats\" to update statistics because it only updates statistics for data that changes. We recommend creating an SQL Agent Job that runs daily or weekly (depending on transaction volume) during off-peak hours to update all statistics for changed data.\n#### Index fragmentation\nAnother important administration task that helps reduce data size and improve performance is to reduce fragmentation for tables and nonclustered indexes. See Resolve index fragmentation by reorganizing or rebuilding indexes<https://learn.microsoft.com/sql/relational-databases/indexes/reorganize-and-rebuild-indexes>.\n#### Other database options\nWe recommend setting the database option PAGE_VERIFY to the value CHECKSUM for all databases (including TEMPDB) because it provides the most robust method of detecting physical database corruption. CHECKSUM is the default setting for new installations.\n### Backup\nSet up backups for both system and user databases. Regularly test restore procedures.\n## Deploy Business Central to Microsoft Azure SQL Database\nYou can deploy a Business Central database to Azure SQL Database. Azure SQL Database is a cloud service that provides data storage as a part of the Azure Services Platform.\nTo optimize performance, deploy the Business Central Server instance that connects to the database on a virtual machine in Azure. Additionally, the virtual machine and SQL Database must be in the same Azure region.\nFor development and maintenance work on Business Central applications, if the Business Central is installed on the same virtual machine in Azure as the Business Central Server, then you can connect to the Azure SQL database from the development environment.\nSee Deploying a Business Central Database to Azure SQL Database<deploy-database-azure-sql-database>.\n## Data encryption between Business Central Server and SQL Server\nWhen SQL Server and Business Central Server run on different computers, encrypt the connection to secure the data channel. See Encrypting Connections to SQL Server<https://learn.microsoft.com/previous-versions/sql/sql-server-2008-r2/ms189067(v=sql.105)>.\n## Integrate directly on SQL Server objects\n> WARNING\n> During operations such as upgrade and app/extension synchronization, the Business Central Server synchronizes the metadata model defined in AL to physical tables on the SQL Server database.\n> While it's possible to integrate directly with SQL Server objects on the database (bypassing the Business Central Server), it's not recommended or even supported.\n> Altering SQL objects created by the Business Central Server directly on the database can break operations such as upgrade and app/extension synchronization.\n> Adding additional SQL objects such as triggers or stored procedures directly on the database can break operations like upgrade and app/extension synchronization, but will also break system integrations that depend on such additional objects if the table schema created by the Business Central Server synchronization changes.\n## Related information\n ../administration/optimize-sql-data-access\n ../administration/troubleshooting-sql-server-connection-problems\n deployment"}