Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Alteryx to Azure SQL Database

kedar26
7 - Meteor

I am doing a data transfer from SAP Hana to Azure SQL Database. The driver which i am using is SQL Server Native 11.0 driver to first make a DSN(64 bit) and my Alteryx installation is also 64bit, once DSN is made i am consuming it to make a connection to Azure SQL to write the data to it. The size of my data tables is large i.e more than 1GB or over 1000000 rows in total. 

 

I am constantly getting the below mentioned errors while loading of the data:

1. The semaphore timeout period has expired. Communication Link Failure.

2. bcp_sendrow failed:TCP Provider: An existing connection was forcibly closed by the remote host.

 

I have attached the screenshot as well. Also note i have tried normal output tool as well as In-DB tool with bulk data load in-db as well, however i still get this issue. I was not facing this issue while I was doing testing on my local MS-SQL Server, also note the MS-SQL Server and Alteryx machine was in the same subnet. Thanks in advance for any help.

 

5 REPLIES 5
BrandonB
Alteryx
Alteryx

"The semaphore timeout period has expired" is generally a network connection issue that results in a server timeout which is external to Alteryx. As a test, can you try the same settings, except instead write a smaller data set of maybe 1000 rows to confirm that the data can be written to the table? That way you will know that the data connection works, it just runs into issues when it loses network connection over a longer period of time. 

kedar26
7 - Meteor

Yes i have tried the smaller tables, only the bigger tables fail. What can be the possible approach I can take further for my client?  

BrandonB
Alteryx
Alteryx

This is a network connection issue, so you are getting some kind of timeout for queries that are running for a longer time. The true fix would be to look at your Windows system logs and see if something is happening like a VPN dropping, network connection being lost, etc.

 

As an alternative, you could try chunking your data sending up subsets of the dataset via a macro if it is the query itself that is timing out. 

kedar26
7 - Meteor

Had a chat with Microsoft Azure Support guys, it was a network configuration which was dropping the connection. Didn't need to subset the data.

teeefarnee
6 - Meteoroid

 Hi may I check how you fixed this?

Labels