CData SQL Gateway Tutorial: ODBC Sources and Remote SQL Access

CData SQL Gateway exposes supported ODBC sources through configured remote interfaces such as MySQL or SQL Server-compatible protocols. Trace the client endpoint to its mapped source, then separate gateway authentication, underlying credentials and the source's actual query capabilities.

Here's a popular CData SQL Gateway video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use CData SQL Gateway Tutorial: ODBC Sources and Remote SQL Access

Frequently Asked Questions

Does the gateway turn every source into native SQL Server?

The gateway exposes a compatible connection interface over supported source access, not a complete replacement of the underlying system. Available SQL operations still depend on the source, driver and gateway behavior.

Why distinguish two sets of credentials?

A client can authenticate to the gateway while the gateway uses a separate identity to reach the source. Both configurations matter, and acceptance at the first boundary does not guarantee access at the second.

What should a connection test verify?

Confirm the intended endpoint, source mapping and a small permitted query. A network handshake alone cannot establish that the configured ODBC source is available or supports the application's required data operation.

Can driver metadata affect client behavior?

Clients can use exposed types and object metadata to construct queries or interpret results. Incorrect assumptions about that mapping can cause failures even when a simple manually written query works.

Where should a failed request be investigated?

Trace the client protocol, gateway logs and underlying driver or source response. Treat them as distinct stages so an authentication problem is not confused with unsupported SQL or invalid source data.