T-SQL surface area in Microsoft Fabric
Applies to: ✅ SQL analytics endpoint and Warehouse in Microsoft Fabric
This article covers the T-SQL language syntax capabilities of Microsoft Fabric, when querying the SQL analytics endpoint or Warehouse.
These limitations apply only to Warehouse and SQL analytics endpoint items in Fabric Synapse Data Warehouse. For limitations of SQL Database in Fabric, see Limitations in SQL Database in Microsoft Fabric (Preview).
Note
For more information on upcoming feature development for Fabric Data Warehouse, see the Fabric Data Warehouse release plan.
T-SQL surface area
- Creating, altering, and dropping tables, and insert, update, and delete are only supported in Warehouse in Microsoft Fabric, not in the SQL analytics endpoint of the Lakehouse.
- You can create your own T-SQL views, functions, and procedures on top of the tables that reference your Delta Lake data in the SQL analytics endpoint of the Lakehouse.
- For more about CREATE/DROP TABLE support, see Tables.
- Fabric Warehouse and SQL analytics endpoint both support standard, sequential, and nested CTEs. While CTEs are generally available in Microsoft Fabric, nested CTEs are currently a preview feature. For more information, see Nested Common Table Expression (CTE) in Fabric data warehousing (Transact-SQL).
- For more about data types, see Data types.
- TRUNCATE Table is supported in Warehouse in Microsoft Fabric.
Limitations
At this time, the following list of commands is NOT currently supported. Don't try to use these commands. Even though they might appear to succeed, they could cause issues to your warehouse.
ALTER TABLE ADD
/ALTER
/DROP COLUMN
- Currently, only the following subset of
ALTER TABLE
operations in Warehouse in Microsoft Fabric are supported:- ADD nullable columns of supported column data types.
- ADD or DROP PRIMARY KEY, UNIQUE, and FOREIGN_KEY column constraints, but only if the NOT ENFORCED option has been specified. All other ALTER TABLE operations are blocked.
- There are limitations with adding table constraints or columns when using Source Control with Warehouse.
- Currently, only the following subset of
BULK LOAD
CREATE ROLE
CREATE USER
- Hints
- IDENTITY Columns
- Manually created multi-column stats
- Materialized views
MERGE
OPENROWSET
PREDICT
- Queries targeting system and user tables
- Recursive queries
- Result Set Caching
- Schema and table names can't contain
/
or\
SELECT
-FOR XML
SET ROWCOUNT
SET TRANSACTION ISOLATION LEVEL
sp_showspaceused
- Temporary tables
- Triggers