Skip to main content

Data Warehouse

New

𝐖𝐚𝐫𝐞𝐡𝐨𝐮𝐬𝐞 𝐚𝐧𝐝 𝐓 𝐒𝐐𝐋 𝐬𝐮𝐩𝐩𝐨𝐫𝐭 - Improve features and avoid limitations

Vote (2) Share
Bamakus Montreuil's profile image

Bamakus Montreuil on 08 Jul 2024 19:22:53

𝐖𝐚𝐫𝐞𝐡𝐨𝐮𝐬𝐞 𝐚𝐧𝐝 𝐓 𝐒𝐐𝐋 𝐬𝐮𝐩𝐩𝐨𝐫𝐭


✔️ Any news about T-SQL DDL ==>

  • alter table add/remove column
  • Identity Columns
  • Primary keys
  • RECORD Columns (store nested fields like json structures)
  • temporary tables (useful on stored proc)
  • Ok, we benefit from Time Travel T-SQL feature, but we also need ==> Temporal Tables for RAW / Staging databases (rows versioning after a merge - Sql server 2022) (useful on storec proc)

and T-SQL DML ==>

  • merge (useful UPSERT on stored proc or for engine DBT compiler) (Type 1 upsert)
  • merge with OUTPUT $action (useful UPSERT + CREATION new current row in case of update) on storec proc or for engine DBT compiler) (Row snapshot , Type 2 versioning)
  • truncate table (useful on stored proc or for DBT engine compiler) (Full refresh)

on Fabric Warehouse ?

Nobody undersand these "super strange" limitations from Microsoft who slow down adoption



✔️ Query activity ==> Offer much more queries history insights

In a hurry to get on Fabric DWH Console similar SQL QUERIES insights as on Bigquery

Very useful to detect query performance ?

  • Volumetry to read (Mb & Rows)
  • Volumetry as result (Mb & Rows)
  • Global & sub tasks query durations
  • Fine Query Plan Presentation => Are we using a T SQL table partition ?

or other DWH feature to reduce SQL query ?

etc ..

Peri Rocha (administrator)

Hello there - thanks for the list. I highly recommend upvoting some of these features which are already on ideas if you haven't yet. Here are some updates regarding your questions: 

- ALTER TABLE ADD/DROP column: we recently shipped this, with some limitations. You can review here: T-SQL surface area - Microsoft Fabric | Microsoft Learn
- IDENTITY columns: we're actively working on this. Comming soon. 
- PRIMARY KEYS: we support it as a table contraint, but we don't enforce it. Did you mean specifically enforcing PK? Would love to learn more about the need for this in warehouse scenarios. Docs here: Primary, foreign, and unique keys - Microsoft Fabric | Microsoft Learn
- TEMP TABLES: we're looking into this right now
- TRUNCATE TABLE: this will be available for the public in the next few weeks

For a view or our immediate roadmap, you can always refer to this article: What's new and planned for Synapse Data Warehouse in Microsoft Fabric - Microsoft Fabric | Microsoft Learn

Thank you so much for the feedback.