Input
SQL Server Database
Reads a whole table or view from a saved Microsoft SQL Server connection.
When to use it
Use it when the data lives in SQL Server and you want it in a pipeline, either straight from a table or through a view that already does the filtering.
In a pipeline
SQL Server DatabaseGroup ByGoogle Sheets Output
Settings
| Setting | Type | Required | Default or hint |
|---|---|---|---|
| Connection | select | Yes | Add a connection below |
| Table | select | Yes | Select a table |
Example
Reading dbo.Customers
- Connection=Finance (SQL Server)
- Table=dbo.Customers
| CustomerId | Name | Region | Balance |
|---|---|---|---|
| C-1041 | Northwind Trading | North | 1240 |
| C-1042 | Harbour Foods | South | 860 |
| C-1043 | Cole & Sons | South | 312.5 |
| CustomerId | Name | Region | Balance |
|---|---|---|---|
| C-1041 | Northwind Trading | North | 1240 |
| C-1042 | Harbour Foods | South | 860 |
| C-1043 | Cole & Sons | South | 312.5 |
The table is read as SELECT * FROM [dbo].[Customers], so the schema stays part of the name.
Worth knowing
- Tables and views are listed as schema.table, for example dbo.Customers; pick the qualified name.
- Views are listed alongside tables, which is the usual way to read a filtered or joined result without a SQL Query node.
- The connection encrypts traffic and accepts a self-signed server certificate unless you turn that off on the connection.
- A named instance belongs in the host as SERVER\SQLEXPRESS, which the SQL Browser resolves; use SERVER,1433 to pin a port instead.