Move SQL Server data into a containerized SQL service ​

A container does not add an ODBC connector to Coordinator DB. Use SQL Server's own client or an export tool to read the source, then send a supported file or row upload to the Coordinator DB endpoint. Treat source access and destination routing as separate checks.

Verify the destination route ​

Inside a container, 127.0.0.1 refers to that container. An importer outside it must use a published host port or an address reachable on the configured container network. Confirm the destination HTTP listener with /ping, then run a small authenticated SELECT from the importer host.

Do not expose an empty-password service broadly to make a connectivity test succeed. Configure credentials and the intended listener before testing the real route.

Transfer a defined dataset ​

Export explicit SQL Server columns to CSV, row-oriented JSON or a compatible Parquet file. Create the destination schema and validate a small batch, paying attention to decimal scale, timestamps, Unicode and nulls. Then transfer bounded batches with recorded source ranges.

If an export or import fails, keep the error attributed to the correct side. Coordinator DB does not manage SQL Server DSNs, drivers or credentials.

See HTTP interface, listener settings and format reference.