current community

your communities

more stack exchange communities

Stack Exchange
tour help
Take the 2-minute tour ×
Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. It's 100% free, no registration required.
up vote 1 down vote favorite
1

I'm experiencing a performance issue with ArcGIS Query Layer using non-sde Sql Server 2008 R2.

Actually, I'm using a rather comprehensive view that pulls and joins data from multiple databases and executes in Sql Management Studio in about three minutes and produces 170k records.

The same query used in a Query Layer definition hangs up for multiple hours. However, limiting the output to 100 records, I was able to create a query layer in ArcMap.

It would be appreciated, if somebody could provide an insight into spatial, attribute indexes and primary keys in relation to query layers. It seems to me that the issue lays in one of the above.

share|improve this question
    
A coworker saw this and saw all of the crazy stuff that was happening when he profiled the database. I don't remember if he found a resolution. I also don't remember the version. I feel like both 10.2 and 10.2.1 had query layer bug fixes. I'll see if I can find out more. –  Jay Cummins Jan 16 at 13:18
    
What we did to work around is unfortunately copying data to a new table and explicitly defining the primary key and index on that field. That made a huge performance boost. It seems to me that ArcGIS is still having issues using database views and query layers, at least with SQL Server database.. –  Matej Jan 26 at 5:30

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.