Forum Discussion

msturzen's avatar
msturzen
Frequent Visitor
4 months ago
Solved

SQL Operator with multiple destinations

Hi all,  a few weeks back I was happy to read the SQL Operator for Eventstream is GA AND supports multiple destinations.  I tried to add a second destination to an existing SQL Operator. That doe...
Eventstream
  • msturzen's avatar
    msturzen
    3 months ago

    As of today 2026-05-11, it works. 
    I wasn't able to get my client to raise a support ticket, so out of curiosity I just retried --> voila, it works perfectly fine. 

    I guess I will never know what the root cause was: feature not rolled out yet, or some kind of defect. 

    Thank you Anonymous  for your help, your ideas and your support. 

    Best

    Martin

Anonymous's avatar
Anonymous
Not applicable
4 months ago

Hi msturzen ,

Your observation that the first SELECT INTO always fails is a really helpful clue.

A couple of things you could double-check:

  • Make sure all output aliases used in the query are explicitly added in the Outputs section of the SQL editor before publishing, and that the names match exactly.
  • If you're using CTEs, ensure they are defined cleanly (preferably within a single WITH block) and that each SELECT INTO works independently.
  • Keep naming simple (avoid special characters) to rule out edge-case issues.

Since one destination works but multiple don’t and the failure always points to the first output this could also be a current limitation or bug in the SQL Operator.

If it still fails, sharing a minimal repro or raising a support ticket would help confirm. As a workaround, using multiple SQL Operators is a practical option for now.

Thanks,
Akhil.