Skip to content
Microsoft SQL Server logoSnowflake logo

Connect Microsoft SQL Server to Snowflake

Move data between Microsoft SQL Server and Snowflake the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Microsoft SQL Server triggers
1
Microsoft SQL Server actions
6
Snowflake triggers
5
Snowflake actions
14

Automation ideas

What you can build with Microsoft SQL Server and Snowflake

A few flows teams run between Microsoft SQL Server and Snowflake. Use one as a starting point, or build your own from scratch.

  • New or Updated Row in Microsoft SQL Server creates Run Query in Snowflake

    Fires when a row is added to, or changed in, a table

  • New Row in Snowflake creates Find Rows in Microsoft SQL Server

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New or Updated Row in Microsoft SQL Server creates Run Multiple Queries in Snowflake

    Fires when a row is added to, or changed in, a table

  • New Row in Snowflake creates Insert Row in Microsoft SQL Server

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

  • New or Updated Row in Microsoft SQL Server creates Insert Row in Snowflake

    Fires when a row is added to, or changed in, a table

  • New Row in Snowflake creates Update Rows in Microsoft SQL Server

    Triggers when a new row is inserted into the selected table. Uses a timestamp column you choose to detect rows added since the last check.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Microsoft SQL Server and acts in Snowflake, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.