dbSlice sample: fix broken foreign keys after lost queue messages, from the command line
Article: https://dbslice.net/blog/fix-broken-foreign-keys-after-lost-messages

01-sqlserver-source.sql   SQL Server: 10,000 generic invoices with 3 lines each (no real data). Run with sqlcmd.
02-postgres-target.sql    PostgreSQL replica with the same foreign key and the lost messages simulated
                          (25 invoices and their 75 lines missing, plus 40 single lines missing). Run with psql.
fk-invoices-check.json    Job: compare invoices (read only).
fk-lines-check.json       Job: compare invoice lines (read only).
fk-invoices-load.json     Job: insert only the invoices missing in the target.
fk-lines-load.json        Job: insert only the lines missing in the target (run it after the invoices).
run-linux.sh              Linux (Docker edition): runs the jobs through the jobs API (curl + jq, token read from a file).
run-windows.ps1           Windows: runs the jobs with dbSlice.exe.

Both scripts load the lines once before the invoices on purpose, to show the foreign key rejecting them.
The job files name connection profiles (MASTER, Server-dbPostg); rename them to your own profiles.
No job file holds a password or a token.
