This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
@RHT2401 What is the full error? Can you elaborate the issue in more detail. Does this error come up when you are trying to connect or when you are trying to run the SQL statement? Are you using In-DB tools or just the regular input tool?
I'm also having this issue. It appears to be happening on the datastream out tool and is hit or miss, as in it happens sometime and other time not. so yes, using in-db connections.
The full message is
Error: Data Stream Out (262): Error SQLExtendedFetch: [Microsoft][SQL Server Native Client 11.0]Error in row[Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 55) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Tool #123 Error SQLExecute: [Microsoft][SQL Server Native Client 11.0][SQL Server]Transaction (Process ID 71) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
Occured on data stream out tool 123
Hit or miss. Happened in the scheduler when it was supposed to run. Manually run it the next day and it runs fine.
I have found that it’s most likely due to resources in the sql server it’s running on. I’ve seen this happen in my desktop too and most of it cleared when I emptied the hard drive off old files that were just consuming space. It could also be other jobs running on the sql server your data source is pulling from too. I’d do what I can to optimize these and see if you still have this error message.