Microsoft SQL Server
Read, write, insert/upsert records, and create-table-if-not-exists against Microsoft SQL Server and Azure SQL, with @p1-bound parameters and double-brace $.path mustache tokens pulled from the flow. Go sibling of the Postgres plugin.
- SDK
- Go
- Protocol
inflowv1- Actions
- 4
- Version
- v0.1.0
- Author
- Inflowenger
- Runs on
- Any
inflowv1host - Categories
- Databases and stores
Reach for it when
SQL Server or Azure SQL — including the branch instance that legally cannot leave the building.
The use people don't expect
Because the plugin runs wherever you start it, the database never has to be reachable from anywhere central. You put a plugin process next to the data and the flow reaches it over NATS.
A flow that uses it
Each one is a shape of flow, not a template to copy. Node names are the labels as they appear on the canvas; a name with a slash means either would do.
Branch data that stays in the branch
Starts withA nightly consolidation.
- MSSQL
A plugin process in the branch reads the local instance. No inbound port opened.
- Code
Aggregates to the figures the centre is allowed to hold.
- CLICKHOUSE
The aggregate lands centrally. The row-level data never moved.
What you getData residency becomes a deployment decision about where a plugin runs, rather than an argument about the architecture.
The reference, not the pitch
This page is about what the plugin is for. Every action, every connection field, the ports, the install one-liner and the caveats are in the catalog entry, which is the thing the maintainer updates.
Near it in the catalog
Many rows, asked questions repeatedly — events, logs, metrics, anything you'll want a GROUP BY over.
DUCKDBDuckDBThe data is files — CSV, Parquet, JSON, Excel — on disk, over https, or in a bucket. SQL over them in place.
MONGODBMongoDBDocuments whose shape you don't want to declare up front.