Anyone successfully using Alteryx with PostgreSQL / PostGIS DB?

[michael_team]

We've been using PostgreSQL 9.3 with PostGIS to serve up data to QGIS and ArcGIS as well as provide multi-user editing for a variety of our data. It's been working wonderfully for two years. We can view/query the data in Alteryx just fine using the 64-bit Spatial ODBC Connection, but all efforts to write/update back to the DB via Alteryx are not working.

Just curious if anyone has a similar configuration, and if you've been able to have success writing / posting back to the PostgreSQL DB via Alteryx?

Thanks!

[rahuls]

Hi Michael,

I would like to know what kind of problem you are actually facing.

The problem that we encounter while updating the data back to DB via Alteryx is that, the datatype of fields automatically changes to "ntext" from "V_WString" datatype, due to which data fails to update. To resolve this we first convert the datatype from "ntext" to "V_String" and then the data gets updated to DB successfully.

Let me know if it helps you.

[michael_team]

Thanks for your repsonse. We are only able to update PostGIS tables that do not have a spatial component. Everything else results in error.

We're using the 64-bit ODBC Driver - Spatial ODBC Connection

No problems viewing the data, just can't write back. 

Are you able to update spatial tables?

[Hollingsworth]

Hi Michael,

I'd like to know if you ever solved this issue. I'm being asked if Alteryx can load spatial data into PostGIS. I assumed it could but then found your post.

Please let me know something either way.

Or if there is an Alteryx moderator watching this thread, please chime in.

Thanks!

John Hollingsworth

[michael_team]

Hey John,
  No, I worked quite a bit testing with their DB specialists, but in the end was told it's a bug that they hope to fix. Haven't heard back in a couple of months. Honestly, it doesn't seem they're very motivated to work with Postgres as (I assume) it's not a common DB platform with their clients. The new In DB processing tools don't support it either. We've just moved forward only utilizing Alteryx/PostGIS as a read-only relationship. Again, it works fine for non-spatial data, but nothing with a spatial object in it.

Hope this helps...

[Hollingsworth]

Thanks Michael.

[michael_team · Accepted solution]

FYI, just got this from Carlos Avila @ Alteryx.... (he's been very helpful btw)

Hi Mike,
 
I wanted to follow up on the issue below. Our development team have looked extensively on making the PostgreSQL 9.3 driver work with the spatial objects in the PostgreSQL database, and have concluded that there is a bug in the driver that prevents this from happening. They recommend that you use the 9.2 driver instead, which works successfully with the spatial objects. Let me know if you have any questions,
 
Carlos

I uninstalled the 9.3 ODBC driver and installed the 9.2 x64 version from here:
http://www.postgresql.org/ftp/odbc/versions/msi/

Reestablished Spatial ODBC connection in Alteryx and so far, everything seems to be working with having Alteryx create/update postgresql/PostGIS data.

Hope this helps.

 

[Hollingsworth]

Outstanding! Thanks for the update.