Disclaimer: This is work in progress intended to consolidate information from various sources for learning purposes. For the latest information please consult the documentation (see the links below)!
Last updated: 25-Feb-2024
[Microsoft Fabric] T-SQL notebook
- {def} notebook that enables to write and run T-SQL code within a notebook [1]
- {feature} allows to manage complex queries and write better markdown documentation [1]
- {feature} allows the direct execution of T-SQL on
- connected warehouse
- SQL analytics endpoint
- ⇐ queries can be run directly on the connected endpoint [1]
- multiple connections are allowed [1]
- allows running cross-database queries to gather data from multiple warehouses and SQL analytics endpoints [1]
- the code is run by the primary warehouse
- used as default in commands which supports three-part naming, though no warehouse was provided [1]
- three-part naming consists of
- database name
- the name of the warehouse or SQL analytics endpoint [1]
- schema name
- table name
- {feature} autogenerate T-SQL code using the code template from the object explorer's context [1] menu
- {concept} code cells
- allow to create and run T-SQL code
- each code cell is executed in a separate session [1]
- {limitation} the variables defined in one cell are not available in another cell [1]
- one can check the execution summary after the code is executed [1]
- cells can be run individually or together [1]
- one cell can contain multiple lines of code [1]
- users can select and run subparts of a cell’s code [1]
- {feature} Table tab
- lists the records from the returned result set
- if the execution contains multiple result set, you can switch from one to another via the dropdown menu [1]
- a query can be saved as
- view
- via 'Save as' view
- {limitation} does not support three-part naming [1]
- the view is always created in the primary warehouse [1]
- by setting the warehouse as the primary warehouse [1]
- table
- via 'Save as' table
- saved as CTAS
- ⇐ 'Save as' is only available for the selected query text
- the query text must be selected before using the Save as options
- {limitation} doesn’t support
- parameter cell
- the parameter passed from pipeline or scheduler can't be used [1]
- {feature} Recent Run
- {workaround} use the current data warehouse monitoring feature to check the execution history of the T-SQL notebook [1]
- {feature} the monitor URL inside the pipeline execution
- {feature} snapshot
- {feature} Git support
- {feature} deployment pipeline support
CTAS - Create Table as Select
T-SQL - Transact SQL