Inconsistency issues with table in datawarehouse

[costinhas75]

Hi,

This is not a 100% data flow related problem, but it might been caused by the slowliness of data flow execution. Currently I have a table that seems to be inconsistent, and doesn't allow me to drop it.

I've checked:

USE Master  
GO  
SELECT session_id, start_time, blocking_session_id  
FROM sys.dm_exec_requests
WHERE status = 'running';

and

USE Master  
GO  
SELECT status   
FROM sys.dm_exec_requests
WHERE blocking_session_id <> 0;

and found some activities running for 3 days now and I killed those.

After that I could insert and delete rows again but I still can't drop it and it seems that is slowing all the ETL. My current DF that adds new rows to that table is running for 1 hour and it usually takes just some minutes (total rows around 60k)

Can you help?

Thanks

[Anonymous]

Hi @costinhas75 ,

Thanks for using Microsoft Fabric Community.

Apologies for the issue you have been facing.

This might require a deeper investigation from our engineering team and they can guide you better.

Please go ahead and raise a support ticket to reach our support team:

https://support.fabric.microsoft.com/support
Please provide the ticket number here as we can keep an eye on it.

[Anonymous]

Hi @costinhas75 ,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. Did you got a chance to create a support ticket? If you have created a support ticket , please do share the same here so that we can also keep an eye on the same.

[Anonymous]

Hi @costinhas75 ,

We haven’t heard from you on the last response and was just checking back to see if you got a chance to create a support ticket. In case if you have created please provide the ticket number here as we can keep an eye on it.
In case if you have any other question on a different issue, we request you to open a new thread .

Thanks,
Gopi Krishna Chenna

[costinhas75 · Accepted solution]

Hi @Anonymous!

First of all thank you so much for your attention to this matter. I've already redirected this issue to the admins of the environment I'm working in, and I think they will open the issue, as I as a normal user don't have that type of ability, I suppose.

I managed to surpass this problem by deleting all LH tables that were being used by the DF and the DF itself, and recreate a new one.

We also found issues when deleting constraings via stored proceduer within a pipeline. These were totally random as far we could understand and it seemed that sometimes it would repeat the same activity twice (e.g., tried to drop the same constraint twice).

Thanks again for your interest

[Anonymous]

Hi @costinhas75 ,

Glad to know your query got resolved. Please continue using Fabric Community for your further queries.