Skip to content

Latest commit

 

History

History
45 lines (38 loc) · 2.76 KB

File metadata and controls

45 lines (38 loc) · 2.76 KB
title Distribution Database | Microsoft Docs
ms.custom
ms.date 03/14/2017
ms.prod sql-non-specified
ms.prod_service database-engine
ms.service
ms.component replication
ms.reviewer
ms.suite sql
ms.technology
replication
ms.tgt_pltfrm
ms.topic article
f1_keywords
sql13.rep.configuredistributionwizard.distributiondatabase.f1
ms.assetid 5b42a083-7a11-41d8-9e3f-320c7c907237
caps.latest.revision 26
author MikeRayMSFT
ms.author mikeray
manager craigg
ms.workload On Demand

Distribution Database

[!INCLUDEappliesto-ss-xxxx-xxxx-xxx-md] 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.

Options

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 [!INCLUDEmsCoName] [!INCLUDEssNoVersion], 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. Paths must refer to disks that are local to the Distributor and begin with a local drive letter and colon (for example, C:). Mapped drive letters and network paths are not valid.

Note

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