Scenarios

Complete, copy-ready SQL Server Agent configurations for the deployments customers run most often, each with the expected run output and downstream setup.

Each scenario is a complete dlh_agent_config.yaml you can copy, fill in and run, followed by what the first and steady-state runs look like and how the data is consumed downstream. The Configuration reference explains every key; these pages show how the keys fit together.

Change Tracking to Delta Lake on Azure and Snowflake

The most common production deployment: CT incremental sync, Delta tables written directly to ADLS, read by Snowflake.

CDC to Apache Iceberg on Amazon S3

Change Data Capture on the source, Iceberg tables and catalog on S3, deletes applied, read by Snowflake or Athena.

SCD Type 2 history tables

Keep every version of every row with a database-level scd2 default and per-table overrides.

Several databases with one agent

Mixed sync modes across databases and choosing a table naming structure that keeps them apart.

Community mode, local only

Evaluate the agent without an account: local Parquet output, the row cap, and the upgrade path.

SQL queries and custom extracts

Ship the results of your own SQL alongside table syncs, to dated or fixed locations.

CI/CD and DBDeux triggers

Kick off dbt transformations after every successful sync via a DBDeux scheduled job or a GitHub Actions dispatch.

How to use these pages

Start from the scenario closest to your target, then layer in the others (for example the SCD2 or SQL query pages on top of the Azure Delta deployment). The YAML fragments compose: each page marks which section it adds or changes.
Replace every <PLACEHOLDER> before the first run. The agent refuses to start while a placeholder remains and names the key.
Validate before scheduling: dlh_agent_sql_server.exe --config-check then dlh_agent_sql_server.exe --diagnose. See CLI reference.
Run once interactively, review the run summary, then hand the run over to Windows Task Scheduler as described in Operations.

Values used in the examples

The examples use agent_version: 1.9.4, a host named sql01.corp.local, Windows paths under C:/dlh/ and the site code Site003 as target_schema_prefix. Change them to match your environment; only the placeholders in angle brackets are mandatory to replace.