Gallery ODBC Connection no longer works with spatial objects as of 2019.3 upgrade

[ccagle]

Hey Everyone, 

I have a workflow on the gallery that started throwing an error with the 2019.3 upgrade we just did 3 days ago. The workflow uses a gallery data connection that is defined as this: 

odbc:DRIVER={ODBC Driver 13 for SQL Server};DATABASE=;SERVER=myServer;Trusted_Connection=yes

to pull back spatial data from SQL server. Prior to our upgrade 3 days ago, there were no issues with this. Now, I cannot pull back the geography data type in SQL server with this connection. Again, this is only after upgrading the server and designer to the latest version of Alteryx (2019.3) three days ago. 

Can anyone assist? 

[MichalM]

@ccagle 

When you say you can't pull back geography data type what do you actually mean? No data is returned in the geography column? Or the data is corrupted?

Are you able to query the SQL server via SQL studio and see the correct result?

[ccagle]

The data is not in the geography format. I don't know if I can say it is corrupted, but it isn't geography / spatial data anymore. And yes, the data on the server is fine...can be queried, used elsewhere, etc. 

[MichalM]

Have you been able to query the data within the SQL Server? Do you get a different result?

[ccagle]

SQL server works fine - there's no issue with the data itself. 

[MichalM]

@ccagle 

I've seen a defect related to use of spatial objects with SQL server which should have been fixed with 2019.3 - see here

If the issue still persists, could you please raise a ticket via support@alteryx.com?