Sign up ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.

We're running into some performance issues when accessing large enterprise geodatabases on a SQL Server 2008 R2 cluster. The database itself performs well and returns queries fine but presenting the information back to ArcGIS for Desktop 10.1 is prohibitively slow.

Connection is direct connect. Data type in SDE is DBO. Machines are VMs with 16Gb RAM.

Are there any tips or tricks or known documents for installs of these on SQL Server clusters where a node instance is presented?

share|improve this question

closed as too broad by PolyGeo Oct 15 at 0:19

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

Welcome to gis.SE. Perhaps you can edit your question (just click edit above) to add details of the type of queries that are causing problems, and some metrics of what is "prohibitively slow"? – BradHards Jun 6 '13 at 9:40
Just to clarify - you're talking about using SDE to store spatial data in SQL server? Or are you using the SQL server native spatial data type? – mapBaker Aug 5 '13 at 18:13

5 Answers 5

See this article: "A common question that I see in Desktop Support is “Why is ArcMap performing so slowly?”"

share|improve this answer

I had a similar problem before and found using PerfQAnalyzer for ArcGIS to be very useful to analyze drawing and fetch speeds in the map.

share|improve this answer

Outside of the maps I found the Process Explorer helpful in getting a grip on what/where the problem was occurring.

Sorry have to keep re-posting as I am only allowed one link per post.

share|improve this answer

This may apply to you (It fixed this same problem for us):

FIX: Performance might be slow when you run a parallel query against a table that has a large amount of spatial data in SQL Server 2008 R2

PS - We just discovered the same problem is back in SQL Server 2012.

share|improve this answer

Depending on whether you are working with ArcSDE Personal, Workgroup, or Enterprise level, your license level may cause limitations.

Take a look here and see if you are extended beyond your license level.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.