SQL Server List Tables¶
Lists all table names in a specified SQL Server schema using saved MSSQL credentials. Loads credentials, calls the backend list-tables operation, and returns a human-readable summary along with structured results.
Usage¶
Use this node when you need to discover or validate the tables available in a given SQL Server schema (e.g., before building queries or selecting a table for downstream operations). Typical workflow: provide your MSSQL credentials, set the schema (dbo by default), optionally adjust timeout, and connect the outputs to nodes that consume JSON or tabular data.
Inputs¶
| Field | Required | Type | Description | Example |
|---|---|---|---|---|
| credentials_path | True | CREDENTIALS | Reference to saved MSSQL credentials matching the 'mssql' template. These credentials are used to authenticate with the database service. | |
| timeout | False | INT | Maximum time in seconds to wait for the operation before timing out. | 60 |
| schema | True | STRING | Name of the database schema to list tables from. | dbo |
Outputs¶
| Field | Type | Description | Example |
|---|---|---|---|
| text | Not specified | Human-readable summary of the operation and the schema’s tables. | Tables in Schema: dbo |
| json | Not specified | Structured results containing the list of tables. | {"tables": ["users", "orders", "products"]} |
| table | Not specified | Tabular representation of the listed tables (typically one row per table). | Not specified |
| extra_1 | Not specified | Reserved/auxiliary output for additional data, if any. | Not specified |
| extra_2 | Not specified | Reserved/auxiliary output for additional data, if any. | Not specified |
Important Notes¶
- The node requires valid MSSQL credentials saved under the 'mssql' credential template.
- Schema is required; if your environment uses non-default schemas, set the appropriate schema name.
- Timeout controls the maximum wait for the backend service; long-running metadata operations may require higher values.
- Outputs include both a readable summary and structured results suitable for downstream parsing.
Troubleshooting¶
- If you receive authentication errors, verify the credentials referenced by credentials_path and ensure the user has access to the target database/schema.
- If the result is empty but no error occurs, confirm the schema name is correct and that it contains tables.
- On timeout errors, increase the timeout input value or check network connectivity to the database service.
- If downstream nodes fail to parse results, connect to the JSON output and validate the structure (e.g., ensure it contains a 'tables' array).