So, for several reasons I created several views on the SQL server whose task was to retrieve data from an Excel file (1 view from a different data source/Excel file) whose purpose was to synchronize the data in the database with the data in Excel and later synchronize this data. will be displayed in the weekly report.

But, Sometimes the process is locked by a wait type “OLEDB”

I can’t find the root use but my biggest problem is that I can’t kill the process using:

KILL <spid>

Then, I also tried using:

KILL <spid> WITH STATUSONLY

"SPID <spid>: transaction rollback in progress. Estimated rollback completion: 0%. Estimated time remaining: 0 seconds."

The process is still running with the query status running with a long execution time and this makes me dizzy when I read an article in Microsoft in the section Detailed blocking scenarios, which states:

an actively running query has acquired a lock, and the lock is not released (affected by transaction level isolation) So another session will wait until they are released.”

And that’s right, all the queries I do on the database are deadlocked. I’ve tried the Resolution they embedded and it still doesn’t work.

I’ve been doing research for a week now, but still haven’t gotten any results.
I would be very grateful, if these seniors could enlighten these laymen.

Thanks.