Ever since we've gone to 10.1 with the direct connect we've had nothing but problems. We've had multiple duplicate key errors and countless snapping issues. The snapping will just at times quit working all together, but strangest we've encountered is snapping issues with a large lake layer. It's located on the SDE and anytime a person goes to edit it the snapping gets killed until a compression is done. I would get it if we did a lot of edits, but all it takes is moving one point in this file and snapping dies for every other layer until a compression is done. We have very few people that look at the layers on the SDE and only two edit on it but we need it to work. Before we upgraded from 10 to 10.1 it worked fine. We have moved several points but haven't really added many so the file size hasn't changed much from then to now. This sounds like the problem I've been experiencing. The data is in feature classes on an Oracle based server in 10.1.1.... Snapping quits until a compression and we can't afford to stop editing to compress multiple times a day... Yes, it's a bulky file with lots of parcels, but there is no network or massive analysis/queries being performed (or attempted), just simple editing. Trying everything I can find in these documents but nothing seems to work. Has anyone had any success in overcoming these issues? Has anyone tried recreating the entire geodatabase since the upgrade? Any other suggestions?
... View more