Mueve las filas sin arruinar el destino Move the rows without wrecking the destination

# binario del releaserelease binary
.\SyncJob.exe --version

# o como herramienta globalor as a global tool
dotnet tool install -g PeopleWorks.SyncJob.Cli
syncjob --version

git clone https://github.com/peopleworks/syncjob.git
cd syncjob
dotnet publish src/SyncJob.Cli/SyncJob.Cli.csproj `
  -c Release -r win-x64 `
  --self-contained true `
  -p:PublishSingleFile=true `
  -p:IncludeNativeLibrariesForSelfExtract=true `
  -o ./publish

{
  "SalesSync": {
    "Source": {
      "ConnectionString": "Server=SRC;Database=App;…",
      "Query": "SELECT Id, Name, Amount FROM dbo.Sales"
    },
    "Destination": {
      "ConnectionString": "Server=DW;Database=Rpt;…",
      "StageTable": "dbo.Sales_Stage",
      "FinalTable": "dbo.Sales"
    },
    "Options": {
      "BatchSize": 10000,
      "MaxDegreeOfParallelism": 4,
      "KeepIdentity": true,
      "MinRowThresholdToCommit": 1000
    }
  }
}

# 1 · conexiones, esquema y mapeos1 · connections, schema and mappings
SyncJob.exe validate -c appsettings.json -s SalesSync

# 2 · ensayo: no escribe una sola fila2 · rehearsal: not one row is written
SyncJob.exe run -c appsettings.json -s SalesSync --dry-run

# 3 · prueba con pocas filas3 · try it with a few rows
SyncJob.exe run -c appsettings.json -s SalesSync --top 100

# 4 · en serio4 · for real
SyncJob.exe run -c appsettings.json -s SalesSync

SyncJob.exe config-init -f fields.txt -o appsettings.json `
  -s SalesSync --stage dbo.Sales_Stage --final dbo.Sales `
  --batch-size 10000 --maxdop 4 --min-commit 1000

Final    →  Final_swap_a1b2c3d4
Stage    →  Final        ← ya cargada, ahora publicada← already loaded, now published
temporal →  Stage        ← datos viejos, se descartan← old data, discarded

# umbral en la corrida, sin tocar el archivothreshold for this run only
SyncJob.exe run -c appsettings.json -s SalesSync --min-commit 1000

# sé lo que hago: publica igualI know what I am doing: publish anyway
SyncJob.exe run -c appsettings.json -s SalesSync --force-commit

# conexiones, esquema y mapeos; nada se escribeconnections, schema and mappings; nothing is written
SyncJob.exe validate -c appsettings.json -s SalesSync

# valida contra la tabla Final (modo directo)validate against the Final table (direct mode)
SyncJob.exe validate -c appsettings.json -s SalesSync --direct

# carga Stage y se detiene antes de publicarload Stage and stop before publishing
SyncJob.exe run -c appsettings.json -s SalesSync --skip-commit

# 100 filas para ver la forma de los datos100 rows to see the shape of the data
SyncJob.exe run -c appsettings.json -s SalesSync --top 100

"Incremental": {
  "Enabled": true,
  "Mode": "RowVersion",
  "TrackingColumn": "RowVer",
  "MergeStrategy": "Upsert",
  "PrimaryKeyColumns": ["Id"],
  "DeleteDetection": "SoftDelete",
  "SoftDeleteColumn": "IsDeleted",
  "SoftDeleteValue": "1"
}

# primera vez: crear la tabla de trackingfirst time: create the tracking table
SyncJob.exe run -c appsettings.json -s SalesSync --init-tracking

# volver a traer todo, ignorando el watermarkpull everything again, ignoring the watermark
SyncJob.exe run -c appsettings.json -s SalesSync --full-refresh

# qué está expuestowhat is exposed
SyncJob.exe secrets status -c appsettings.json

# cifrar cada contraseña del archivoencrypt every password in the file
SyncJob.exe secrets protect -c appsettings.json

# para un servicio: alcance de máquinafor a service: machine scope
SyncJob.exe secrets protect -c appsettings.json --scope machine

# 1 · conexiones1 · connections
SyncJob.exe connection add source `
  --server SQL01 --database SourceDB `
  --username etl --password "secret"

SyncJob.exe connection add dest `
  --server SQL02 --database DestDB `
  --username etl --password "secret"

SyncJob.exe connection test source

# 2 · configuración2 · config
SyncJob.exe config create sales `
  --display-name "Sales Sync" `
  --source-conn source --dest-conn dest `
  --source-query "SELECT Id, Name, Amount FROM dbo.Sales" `
  --dest-stage dbo.Sales_Stage --dest-final dbo.Sales

# 3 · mapeos3 · mappings
SyncJob.exe mapping add sales `
  --source Id --dest Id --primary-key
SyncJob.exe mapping add sales `
  --source Name --dest Name

# 4 · ejecutar4 · run it
SyncJob.exe run-db sales --dry-run
SyncJob.exe run-db sales

SyncJob.exe history list
SyncJob.exe history list sales --status Failed --limit 20
SyncJob.exe history show <execution-id>
SyncJob.exe history stats --days 30
SyncJob.exe history clear --older-than 90

SyncJob.exe db info
SyncJob.exe db backup --output C:\Backup\syncjob.db
SyncJob.exe db restore --file C:\Backup\syncjob.db
SyncJob.exe db cleanup --older-than 90
SyncJob.exe db vacuum

SyncJob.exe run `
  -c C:\SyncJob\appsettings.json -s SalesSync `
  --min-commit 1000 `
  --log-file C:\Logs\sync.sales.log `
  --log-level Info --json-log --quiet

# archivo diario automático en un directorioauto-dated daily file in a directory
SyncJob.exe run -c config.json -s SalesSync `
  --log-level Debug --log-dir C:\Logs

New-Service -Name "PeopleWorks SyncJob" `
  -BinaryPathName "C:\SyncJob\SyncJob.exe" `
  -StartupType Automatic `
  -DisplayName "PeopleWorks SyncJob Service"

Start-Service "PeopleWorks SyncJob"