SQL Server Enterprise Geodatabase slow performance with M values?

Question

Has anyone seen performance issues when using SQL Server Esri Enterprise Geodatabase with data that have M values. We are running across slow draw times on all of our GIS datasets that were derived from our LRS network GIS layer. The same datasets will draw within 1 second in a file geodatabase vs in sql will take 10-15 seconds.

Thanks,

Claire

ScottFierro2 · Answer

OK, not exactly what we discovered but will toss it out there for you as an option to consider. In this other post I gave the link to original post where I broke down details regarding modification of the disc storage drive configurations used behind the scenes of SQL Server. While this may not fix this issue for you I'd still suggest checking it out as it's proven to provide significant performance gains for us and many others using SQL.

https://community.esri.com/thread/200309-system-design-strategies-and-performance

ClaireInbody1 · Answer

We are seeing it only on feature classes with M values. SQL Server version 2016.

ScottFierro2 · Answer

Is this issue specific to only feature classes which have M values or do you experience the same slowness with other feature classes that don't have M values?

What version of SQL Server are you using?