I am aware that reading spatial data from SQL to Alteryx seems to only work when using the SQL Server Native Client driver. This is discussed in more detail here:
However, with the latest release of SQL Server Management Studio (v19), they no longer support the Native Client driver, it uninstalls it from your machine. It is now recommended by Microsoft by you use Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL).
However, this driver doesn't appear to support geography/geometry spatial data types in SQL. This seems like a very strange decision and impacts a lot of our spatial processes for those have updated to SSMS v19.
Does anyone have any thoughts or ideas on this?
It seems strange that we might need to download the now-deprecated Native Client driver to still be able to read spatial data types into Alteryx.