This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I was able to connect to SDE through alteryx. However, alteryx is reading the data without spatial objects. Does the spatial object stored as a different file? If so, how to import it with the data table?
Spatial Database Engine is currently not supported in Alteryx. I have placed a feature request with our Products team. Alteryx does support a variety of other formats including .GDB. Would it be possible for you to use .GDB?
I have successfully connected to our SQL server SDE DB using Alteryx. I found the key to being able to access the spatial object is to make sure it is the last column in the table, which you can do via the SELECT query. Otherwise it will pull in all the columns OK but the SpatialObj column comes in as <NULL>.
I've tried the same connecting in our Oracle Database, but didn't work. Also tried to follow these steps https://support.esri.com/en/technical-article/000009667 and the following error message is displayed: "Error OCIStmFetch: ORA-21500: internal error code, arguments: [%s],[%s],[%s],[%s],[%s],[%s],[%s],[%s]]".
I came across the same error and st_geometry looks to be the culprit. one of the workarounds is to ask your DBA to have the data type change to sdo_geometry and it will work fine. I have a view on top of my table and the view has sdo_geometry as the datatype for that column ( check to make sure there are no other st_geometry columns)