Opening the attribute table for a Snowflake query layer containing polyline spatial data causes ArcGIS Pro to crash.

Additional Information

Workaround

Define the table schema with smaller column lengths for the VARCHAR columns. This eliminates the crash when opening the attribute table in ArcGIS Pro for this data.

It is recommended that when the column data is predictable, the user needs to specify or define an appropriate column length. Many of these columns in the table are Y or N values and do not warrant the max length for this data type.

When to specify column length:

Snowflake compresses column data effectively; therefore, creating columns larger than necessary has minimal impact on the size of data tables. Likewise, there is no query performance difference between a column with a maximum length declaration (e.g., VARCHAR(16777216)) and a smaller precision.

However, when the size of the column data is predictable, Snowflake recommends defining an appropriate column length for the following reasons:

• Data loading operations are more likely to detect issues such as columns loaded out of order, e.g., a 50-character string loaded erroneously into a VARCHAR(10) column. Such issues produce errors.
• When the column length is unspecified, some third-party tools may anticipate consuming the maximum size value, which can translate into increased client-side memory usage or unusual behavior.

Refer to the following documentation for additional information: https://docs.snowflake.com/en/user-guide/table-considerations.

Steps to Reproduce