Error: Underlying DBMS error [[Microsoft][ODBC Driver 18 for SQL Server][SQL Server] The geometry data type cannot be selected as DISTINCT

TommyJackson

Since upgrading to ArcGIS Enterprise 11.5, we’ve started seeing the following recurring error in ArcGIS Server Manager:

Error:
Underlying DBMS error [[Microsoft][ODBC Driver 18 for SQL Server][SQL Server] The geometry data type cannot be selected as DISTINCT because it is not comparable.]
Layer: SURVEY_POINTS (STATE_ID = 0)

This seems to occur on feature layers that are sourced from spatial SQL views (geometry included). In many cases the dashboards that use these layers appear to function normally, but in others we’ve noticed strange behavior — especially when layer actions, map actions, or table selections are triggered. It’s most noticeable when using:

• Categories from Grouped Values

• Actions that cause repeated panning/zooming or iterative queries

In some dashboards it almost appears to get stuck in a loop of requests, which lines up with the DISTINCT-on-geometry issue.

My questions:

1. Should I be concerned about these errors appearing even in dashboards that seem stable and responsive?

   • Is this something that can cause long-term performance issues or instability even if the dashboard appears fine?

2. What is the recommended way to prevent “geometry is not comparable for DISTINCT” errors with layers derived from spatial SQL views?

   • Are there Arcade or Dashboard configuration changes that could eliminate DISTINCT queries (e.g., avoiding certain grouping/filters)?

3. Is there an Enterprise 11.5 change that made this more common or more aggressively logged compared to prior versions?

Any guidance or recommended patterns for building stable spatial SQL views for Enterprise 11.5 dashboards would be greatly appreciated.

TommyJackson

The only performance issue that I see seems to be cluttering of the logs. In my case it seems to be dashboards using the Table Type of Grouped Values that triggers it.