Error Message to Complete SQL Query for Input

[Ewbkm]

Hi

I can successfully run the codes and get results if I run the query directly in MicroSoft SQL Server.  In Alteryx, in SQL editor I would get a success test message " A successful connection was made and no errors were found parsing the query" and get an error message

"Error: Input Data (1): Error SQLExecute: [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Internal Query Processor Error: The query processor could not produce a query plan. For more information, contact Customer Support Services." once I run the workflow.  

Does anyone know how to fix this or know the possible reasons for this error? Thanks.

[KGT]

Some things to check:

• Does it work if you use the native SQL Driver instead of ODBC?
• Is the query simple, intermediate, or advanced... does it have things like cursors, multiple DB Servers, different schemas etc? (I don't think it would pass the test in most of these cases though).
• Does the same work using the In_DB tools?

I'm not sure what the issue is, as I have no idea what you're doing/running, but the error seems to be something that the driver needs for the query.

[Ewbkm]

The query works in the native SQL driver environment and it's not complicated, which are with an inner join of two tables stored in the same server.  

When you say it's something the driver needs for the query, is it something I can fix in Alteryx setup or it's something IT need to check from SQL server side?

Thanks.

[KGT · Accepted solution]

If it works in Alteryx using the Native SQL driver, then it must be something on the ODBC Driver. v17 is not outdated and so I'm not sure what it could be, maybe an SSL config on the SQL server or something as I believe there's been updates that the v18 driver handles. I'm far from an expert on that though and tend to stay away from networking issues when I can.

I would flick over to the Native Driver (either Quick Connect or OleDB) for now, and log a ticket with your IT explaining the difference in being able to execute. They may have some advice on the ODBC Driver working. The only thing you could really do I think is update to v18 of the ODBC Driver.

[apathetichell]

Here's some Stack Overflow comments on this:

https://stackoverflow.com/questions/78638734/how-to-avoid-sqlserverexception-the-query-processor-ran...