SQLDistributions extends the T-SQL scripting environment to by adding support for modelling and analysing probability distributions directly within the database. Performing data analysis from within the database tends to be much faster and more efficient than transporting the data across the network to a client application, and also allows simpler and cleaner application architectures. The distributions are all implemented as CLR-based user-defined types, each supporting a broad range of methods for calculating descriptive statistics (mean, median, mode, skewness, kurtosis etc) and other distribution characteristics. Each distribution also provides a random-number generator which uses modified ziggurat methods to enable high-speed, high-volume generation of random variates that fit the distribution profile. Supported distributions include: (Continuous) – Beta – Cauchy – Chi-squared – Exponential – F – Gamma – Gumbel – Inverse chi-squared – Inverse gamma – Laplace – Logistic – Log-normal – Non-central beta – Non-central chi-squared – Non-central F – Non-central T – Normal – Pareto – Rayleigh – T – Triangular – Uniform – Weibull (Discrete) – Bernouilli – Binomial – Hypergeometric – Negative binomial – Poisson

The SQL Distribution control is implemented as a Microsoft® ActiveX® in-process component. It provides a way to move schema and data to Subscribers for snapshot replication and to control the synchronization of subscriptions for transactional replication. The control is comparable to the Distribution Agent. Its primary class, the SQLDistribution object, includes the ability to:

• Add, drop, copy, and register subscriptions for synchronization using Windows Synchronization Manager. For more information, see Common SQL Distribution Control and SQL Merge Control Functionality.
  
  
• Specify an alternate snapshot folder from which the initial snapshot for a subscription can be applied.
  
  
• Specify a working directory to which snapshot files are copied when File Transfer Protocol (FTP) is used to retrieve the initial snapshot.
  
  
• Generate a specially formatted subscription file (usually an .msf) in a specified location. These files can be attached to create a synchronized subscription that is registered at the Publisher as part of an attachable subscription database.
  
  
• Specify a Data Transformation Services (DTS) package that transforms command rowsets before applying them to a Subscriber.
  
  
• Set the Subscriber options to immediate updating or queued updating for changes made at the Subscriber.
  
  
• Synchronize push, pull, or anonymous subscriptions in a transactional publication.

SQLDistributions extends the T-SQL scripting environment to by adding support for modeling and analyzing probability distributions directly in the database.

Performing data analysis from within the database tends to be much faster and more efficient than transporting data over the network to client applications, and also allows for a simple and clean application architecture.

The distributions are all implemented as CLR based user-defined types, each supporting various methods for calculating descriptive statistics (mean, median, mode, slope, kurtosis etc.) and other distribution characteristics.

Each distribution also provides a random-number generator that uses a modified ziggurat method to allow high-speed, high-volume generation of random variates that fit the distribution profile.

Supported distributions include:

(Continuous) – Beta – Cauchy – Chi-squared – Exponential – F – Gamma – Gumbel – Inverse chi-square – Inverse gamma – Laplace – Logistics – Normal entry – beta Non-middle – Non-central chi-square – Non center F – Non-center T – normal – Pareto – Rayleigh – T – Triangle – Uniform – Weibull

(Discrete) – Bernouilli – Binomial – Hypergeometric – Negative binomial – Poisson

Condition :

SQL Server 2005 or later

Limitations:

30-day trial

7 May 15 In Developer tools, Components & libraries

This unofficial build chart lists all of the known Service Packs (SP), Cumulative Updates (CU), patches, hotfixes and other builds of MS SQL Server 2022, 2019, 2017, 2016, 2014, 2012, 2008 R2, 2008, 2005, 2000, 7.0, 6.5 and 6.0 that have been released.

Useful articles:

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 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.