Issue with snapping and performance speed

17333
34
01-06-2012 09:49 AM
AngelaHansen
New Contributor
Hi All,

We have been encountering problems lately while editing (using 10 sp 2). The speed of ArcMap while editing slows to a crawl, and snapping will not work (unless classic snapping is enabled).

I was wondering if anyone else has encountered this issue?

Thanks,
Angela
Tags (2)
0 Kudos
34 Replies
dartonCharles
New Contributor
Hello everyone,
                     I've been having a serious issue after i upgraded from 10 to 10.1. The speed of the software decreased significantly when editing. If i had to select a line it would take a long time to show and its not because of my machine because it was recently upgraded as well. Also my snapping doesnt seem to work at all even though i turn all the options on. Arcmap is really slow in 10.1 for me so i dont know if anyone has a solution for this. I can really use some help please.
0 Kudos
SherryLufkin
New Contributor
Just installed 10.2 and I am experiencing snapping problems also.  Snapping works fine unless I try to snap to a layer that is joined to a table. Is anyone experiencing the same problem?  Is there a solution besides 'unjoining' the table?
0 Kudos
KevinHighland
Occasional Contributor II
This might help others using MSSQL 2008.

(Our problems revolved around very slow snapping, measure tool and any queries)

The SQL Spatial types have impaired our performance greatly. When running the same problematic features as SDEBinary, in the same Dataset, our performance issues are gone. Is this a fix for all using MSSQL 2008? I can't say that for sure, but it definitely has made a big difference on our data.

If you are running a similar setup. Simply copy and paste a feature into the same Dataset, and change the keyword to SDEBinary. If you don't see SDEBinary, you may be setup where the Binary option is your default. You could check DBTune to see the default "GEOMETRY_STORAGE", ours is set to "GEOMETRY".

Good luck.


We were having very poor performance since upgrading from 10.0 to 10.1 and this was the solution. An easy way to see your geometry storage type is to check the auto shape and length fields in a polygon feature class. If you are seeing "SHAPE.STArea()" and "SHAPE.STLength()" then you are using the SQL spatial type. The SDE Binary spatial type will show "Shape.area" and "Shape.length." I pulled copies of a few feature classes (duplicates, but one using SQL spatial and the other using SDE spatial) into an MXD and the difference between the two sets was staggering. Draw times with the SDE were four times faster than draw times with SQL. Snapping was not working with SQL, but worked perfectly with SDE.

This is all on our publication database that is made up of handful of replicas. When we upgraded to 10.1, the default geometry storage type was change to SQL and then we recreated the entire pub database, so all feature classes were then using the SQL geometry. It only affected feature classes that were created since the upgrade. After making the changes Tesla described above and recreating the pub database, our problems disappeared!

Hopefully this helps some of you.
DavidMajor
New Contributor II

This was also the solution for us, thanks!!! We have SQL 2008 R2 and ArcGIS 10.3.1. I did just loke Kevin mentioned, copied and pasted the feature classes into the same dataset, and changed the keyword to SDEBINARY. Then I deleted the old feature classes, renamed the new ones. I also used the batch create spatial indexes since those were gone, but the attribute indexes copied over fine.

I also noticed that this improved the performance when SELECTING features, especially annotation.

David

0 Kudos
JohnMorley
New Contributor II
I am also seeing issues with snapping to any layer that is joined to a table in ArcMap 10.2.   Removing the join makes snapping to that layer work again, and adding a join to any layer disables snapping to that layer.


Just installed 10.2 and I am experiencing snapping problems also.  Snapping works fine unless I try to snap to a layer that is joined to a table. Is anyone experiencing the same problem?  Is there a solution besides 'unjoining' the table?
0 Kudos
JasonLyon
New Contributor III
I am also seeing issues with snapping to any layer that is joined to a table in ArcMap 10.2.   Removing the join makes snapping to that layer work again, and adding a join to any layer disables snapping to that layer.


I am having same issues, if I have a layer with a table join, snapping does not work, but once join is removed it works fine.
Very annoying to have to add and remove constantly.
0 Kudos
RichardFairhurst
MVP Honored Contributor
I am having same issues, if I have a layer with a table join, snapping does not work, but once join is removed it works fine.
Very annoying to have to add and remove constantly.


You can add an unjoined copy of the layer to the map so that you don't have to break and recreate the join all the time.  Just turn the unjoined snapping layer on and off if it messes up your cartography.  I tested this workaround and it works.  Either way, I can reproduce the fact that the join causes snapping to fail on the actual joined layer so I will report it to ESRI on Monday.
0 Kudos
WeisenGao
New Contributor
I have been encountering problems lately while editing (using 10.1 sp1). The speed of ArcMap while editing slows to a crawl, and snapping will not work

I was wondering if anyone else has encountered this issue?
0 Kudos
TraciMeulemans
New Contributor II
Snapping does not work for me either. I am on 10.2.2.
0 Kudos
TraciMeulemans
New Contributor II
Snapping does not work for me either. I am on 10.2.2.


I had to create a new mxd and that fixed the snapping issues for me.
0 Kudos