Error SQLExecute: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot bulk load

Question

Hi all,

I'm trying to fix a workflow that hasn't been running as it should. The workflow inputs data from an Azure SQL DB using ODBC connection. The connection appears to fine (at least from what I can tell) as I can access the visual query builders to see the tables in the database and write the SQL query in input from my desired table.

However, the issue is when I run the workflow, I get various errors each time like the following:

Error SQL Execute: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot bulk load because the file "XXXX.csv" could not be opened. Operating system error code 12(The access code is invalid.)

OR

Error SQL Execute: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot bulk load because the file "XXXX.dbo.XXX" is incomplete or could not be read. Operating system error code 12(The access code is invalid.)

I have done a few tests like updating the SQL query to input only the top 10 records from the table and this runs fine with no errors. The workflow fails every time I try to select all records from the table (e.g. select * from table)

Any help would be appreciated

Felipe_Ribeir0 · Answer

Hi @nhartin

This seems to be a known issue from the Azure side, so it is probably a good idea to see how people are doing to avoid it and adapt what they suggest to Alteryx.

https://learn.microsoft.com/en-us/answers/questions/988935/cannot-bulk-load-file-error-code-12-azure-synapse

https://stackoverflow.com/questions/69000695/azure-synapse-cannot-bulk-load-because-the-file-could-not-be-opened-operating

https://www.google.com/search?q=%22Azure%22+is+incomplete+or+could+not+be+read.+Operating+system+error+code+12%28The+access+code+is+invalid.%29&newwindow=1&sxsrf=AJOqlzUpFtD3RtW4UZ_wV9vxW3eiTvllcA%3A1674040454145&ei=htTHY7_JCMvN1sQPwtmH0AY&ved=0ahUKEwi_pO_U_tD8AhXLppUCHcLsAWoQ4dUDCA8&uact=5&oq=%22Azure%22+is+incomplete+or+could+not+be+read.+Operating+system+error+code+12%28The+access+code+is+invalid.%29&gs_lcp=Cgxnd3Mtd2l6LXNlcnAQAzoKCAAQRxDWBBCwAzoECCMQJ0oECEEYAEoECEYYAFD6GVixN2CjOmgCcAF4AYABbIgBggSSAQMxLjSYAQCgAQHIAQbAAQE&sclient=gws-wiz-serp

nhartin · Answer

Ok I've managed to get a couple of successful runs; I believe the issue is the table in the DB is constantly being updated by other processes and when the workflow is run at the same time it causes the errors seen above. In this case how can I ensure that my workflow will not fail? Is there a pre-sql statement I can run to ensure the table can be read? or a way to keep looping through the dynamic input until it's successful?