Distribution Database

Applies to: SQL Server Azure SQL Managed Instance

The distribution database stores metadata and history data for all types of replication, and transactions for transactional replication.

In many cases, a single distribution database is sufficient. However, if multiple Publishers use a single Distributor, consider creating a distribution database for each Publisher. Doing so ensures that the data flowing through each distribution database is distinct. You can specify one distribution database for the Distributor using the Configure Distribution Wizard. If necessary, specify additional distribution databases in the Distributor Properties dialog box.


Distribution database name
Enter a name for the distribution database. The default name for the distribution database is 'distribution'. If you specify a name, the name can be a maximum of 128 characters, must be unique within an instance of Microsoft SQL Server, and must conform to the rules for identifiers. For more information, see Database Identifiers.

Folder for the distribution database file and Folder for the distribution database log file
Enter the path for the distribution database and log files. If using the SQL Server Management Studio GUI, paths must refer to disks that are local to the Distributor and begin with a local drive letter and colon (for example, C:). If using Transact-SQL (T-SQL), supported UNC path formats for SMB file shares are valid. See more information in SQL Server with SMB fileshare storage.


You can decrease the time it takes to write transactions and improve the performance of replication by placing the distribution database log on a separate disk drive from the distribution database.

See Also

Configure Distribution
Configure Publishing and Distribution
View and Modify Distributor and Publisher Properties