Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
I'm reading MS documents, it shows Fabric warehouse supports time travel via T-SQL:
SELECT *
FROM [dbo].[dimension_customer] AS DC
OPTION (FOR TIMESTAMP AS OF '2024-03-13T19:39:35.28');
However, it doesn't mention how to get a version history of the warehouse table. In Lakehouse, I can get version history via the code below. But it doesn't work in warehouse, is there an equivalent t-sql command for warehouse tables?
Solved! Go to Solution.
Hi @Jeanxyz,
So you're wanting to see all history for a table? This isn't possible directly with TSQL.
You will need to use OneLake Explorer to get at the delta logs, and then parse all the delta logs for the table to get this type of information I think.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
The T-sql snippet works, but I'm really interested in getting the full version history of a warehouse table, not a specific version.
It looks T-sql only allows me to get the current version. But the command is strange, it doesn't specify the version id refers to which warehouse table. Does that mean the whole warehouse shares one version id?
SELECT CURRENT_TIMESTAMP
Hi @Jeanxyz ,
Thank you @tayloramy for the response provided!
Has your issue been resolved? If the response provided by the community member addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.
Thank you for your understanding.
Hi @Jeanxyz,
So you're wanting to see all history for a table? This isn't possible directly with TSQL.
You will need to use OneLake Explorer to get at the delta logs, and then parse all the delta logs for the table to get this type of information I think.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Hi @Jeanxyz,
The describe history command is a Spark SQL command, not a T SQL command.
The SQL endpoint for a warehouse only supports T SQL, not Spark (Spark is primairly used in notebooks which connect much better to lakehouses)
Is the TSQL snippet you added from the documentation not working in the warehouse SQL endpoint?
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.