SQL Server database handler

The SQL Server database handler is a part of the Ekobit.BizDataX.Databases.MSSQL NuGet package which has to be installed before the handler can be used. It is used by the BizDataX Designer.

Table of contents
Installation
Settings
SQL Server specific settings
Example
Client-side parallelism
SQL Server Types

Installation

The installation of the database handlers is described in more detail in the installation guide.

Once installed, it provides a way to configure repeating persistence and restartability store settings in App.config file.

Settings

The settings are set in Package.xaml file for each handler, inside the iterator blocks.
Settings are constructed using Fluent Handler API.
SQL Server handler extends those setting with some database specific options.

SQL Server specific settings

Extends Setting Description Data type
.WithBulk CreateIndexOnTempTables If true, after creating temporary tables when preparing for masking, an index will be created on those tables. This can affect performance both positively and negatively. Default is true. Boolean
.WithBulk UseMerge If true, after bulk insert temporary table will merge with original table using merge statement. Otherwise it will truncate original table and insert new values. Default is true. Boolean
.WithSegments ByPartitions Sets ranges defined by SQL Server range-partitioned tables.

Example

Customer.Handle.WithSegments().ByPartitions().WithBulk().CreateIndexOnTempTables(true)

Client-side parallelism

By default, BizDataX only uses server-side parallelism.

To set the level of client-side parallelism, in the Package.xaml file click on a Masking engine, in the Properties pane find MaxParallelIterators and set it to the desired number.

The optimal number of iterators should be close to the physical CPU core count.

SQL Server Types

If upon running a sensitive data discovery on BizDataX Portal or upon running a package in Visual Studio or on BizDataX Portal, you encounter the exception like in Figure 1 or a similar error, download and install the SQLSysClrTypes.msi file from the appropriate Microsoft SQL Server Feature Pack.

Icon
Figure 1: SQL Server Types exception