risingwavelabs/risingwave · error · SinkError

SQL Server error

Error message

SQL Server error: {0}

What it means

Sentinel variant of the SinkError enum wrapping any anyhow error raised by the SQL Server sink connector. It is applied uniformly to all SQL Server-specific failures (connection, query execution, bulk copy) so downstream code can classify the sink backend by variant; the inner anyhow error holds details.

Solutions

  1. Inspect the wrapped anyhow error for the underlying SQL Server failure (connection, TDS protocol, query errors).
  2. Verify connection string, credentials, and network reachability to the SQL Server instance.
  3. Check server-side errors such as lock timeouts or invalid schema and fix the sink mapping accordingly.
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at src/connector/src/sink/mod.rs:1208 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of risingwavelabs/risingwave@6469eb736d (2026-09-11). Data as JSON: /api/errors/d861ef9551530bec. Report an issue: GitHub.

Appendix: source

Thrown at src/connector/src/sink/mod.rs:1208

    #[error(transparent)]
    Internal(
        #[from]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("BigQuery error: {0}")]
    BigQuery(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("DynamoDB error: {0}")]
    DynamoDb(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("SQL Server error: {0}")]
    SqlServer(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error("Postgres error: {0}")]
    Postgres(
        #[source]
        #[backtrace]
        anyhow::Error,
    ),
    #[error(transparent)]
    Connector(
        #[from]
        #[backtrace]
        ConnectorError,
    ),
    #[error("Secret error: {0}")]

View on GitHub (pinned to 6469eb736d)