Fabric Warehehouse stuck

Hello Nameless_LW 

The query “SELECT * FROM mySchema.myTable WHERE 1=2” is auto-generated—typically when “Auto create table” is enabled in your pipeline—to validate or create a destination table. This query is holding locks or running within a transaction, which is causing blocking on your warehouse

• When you try to kill its session, it doesn’t disappear immediately but goes into a “KILLED/ROLLBACK” state. This is normal behavior: once a session with open transactions is killed, SQL Server (and Fabric’s SQL engine) must roll back any changes to maintain transactional consistency. Unfortunately, if the rollback involves many changes or locks, this operation could take a very long time.

Here is what could help :

Use your query (joining sys.dm_exec_requests and sys.dm_exec_sql_text) to check which session is blocking others.

Once confirmed, running
  KILL session_id;


followed by
  KILL session_id WITH STATUSONLY;

will report the rollback progress. (Be aware that if the rollback is heavy, you might have to wait for it to finish.)

If the rollback never completes or if the blocking query persists for an inordinate amount of time, then this might indicate an underlying issue with the Fabric Warehouse engine. Open a support ticket

If this is helpful please accept the answer