Skip to main content

​
Overview

Wirekite supports SQL Server 2016 and above as a target database for:
  • Schema Loading - Create target tables from Wirekite’s intermediate schema format
  • Data Loading - Bulk load extracted data using ODBC bulk copy
  • Change Loading (CDC) - Apply ongoing changes using MERGE operations
SQL Server loaders use ODBC bulk copy for high-performance data loading. The Change Loader uses shadow/merge tables with _wkm suffix for atomic change application.

​
Prerequisites

Before configuring SQL Server as a Wirekite target, ensure the following requirements are met:

​
Database Configuration

  1. Version: SQL Server 2016 or above
  2. ODBC Driver: Install ODBC Driver 18 for SQL Server on the loader host
  3. User Permissions: Create a dedicated Wirekite user with:
    • CREATE TABLE privilege
    • INSERT, UPDATE, DELETE on target tables
    • Read/write access to Wirekite internal tables (wirekite_progress and wirekite_action)

​
File System Access

  • Ensure the user running Wirekite has write permissions to the work directory
  • Verify sufficient disk space for intermediate files during change loading
Use the Wirekite cmdline tool or sqlcmd to verify database connectivity before running loaders.

​
Schema Loader

The Schema Loader reads Wirekite’s intermediate schema format (.skt file) and generates SQL Server-appropriate DDL statements for creating target tables.
The Schema Loader generates both base tables and merge tables (with _wkm suffix) for CDC operations.

​
Required Parameters

​
string
required
Path to the Wirekite schema file (.skt) generated by the Schema Extractor. Must be an absolute path.
​
string
required
Output file for CREATE TABLE statements. Includes both base tables and merge tables for CDC operations.
​
string
required
Output file for constraint definitions (indexes, unique constraints, check constraints).
​
string
required
Output file for FOREIGN KEY constraints. Can be applied after initial data load for better performance.
​
string
required
Absolute path to the log file for Schema Loader operations.

​
Optional Parameters

​
string
default:"none"
Output file for DROP TABLE IF EXISTS statements. Set to “none” to skip generation.
​
string
default:"none"
Output file for recovery table creation SQL. Set to “none” to skip.
​
boolean
default:"true"
When true, generates merge tables (_wkm suffix) for CDC operations. Set to false if only doing data loads without change capture.
​
boolean
default:"false"
When true, only creates merge tables, skipping base table creation.

​
Data Loader

The Data Loader reads Wirekite’s intermediate data format (.dkt files) and loads records into SQL Server target tables using ODBC bulk copy for high performance.

​
Required Parameters

​
string
required
Path to a file containing the SQL Server connection string.
Connection string format:
Example:
​
string
required
Directory containing data files (.dkt) to load. Files are processed in parallel based on maxThreads.
​
string
required
Path to the Wirekite schema file used by Schema Loader. Required for table structure information.
​
string
required
Absolute path to the log file for Data Loader operations.

​
Optional Parameters

​
integer
default:"5"
Maximum number of parallel threads for loading tables. Each thread loads one table at a time.
​
boolean
default:"false"
Set to true if data was extracted using hex encoding instead of base64.
​
boolean
default:"true"
When true, indicates the database is remote. Affects how bulk copy operations are performed.
For best performance, set maxThreads equal to the number of CPU cores available on the loader host.

​
Change Loader

The Change Loader applies ongoing data changes (INSERT, UPDATE, DELETE) to SQL Server target tables using MERGE operations with shadow tables.
The Change Loader requires merge tables to be created by the Schema Loader. It processes up to 8 concurrent MERGE operations.

​
Required Parameters

​
string
required
Path to a file containing the SQL Server connection string.
Connection string format:
​
string
required
Directory containing change files (.ckt) from the Change Extractor.
​
string
required
Working directory for temporary CSV files during merge operations. Must be writable.
​
string
required
Path to the Wirekite schema file for table structure information.
​
string
required
Absolute path to the log file for Change Loader operations.

​
Optional Parameters

​
boolean
default:"true"
When true, loads changes locally. When false, uses remote loading methods.
​
integer
default:"60"
Maximum number of change files to process in a single batch before executing MERGE operations.
The Change Loader should not start until the Data Loader has successfully completed the initial full load.

​
Orchestrator Configuration

When using the Wirekite Orchestrator, prefix target parameters with target.schema., target.data., or target.change. depending on the operation. Example orchestrator configuration for SQL Server target:
For complete Orchestrator documentation, see the Execution Guide.