nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Editor Tracking 10.1 Issues

TedCronin

Enabling Editor Tracking in 10.1, prevents a user from accessing a 10.0 SDE Geodatabase with 10.0 Client.

Finde mehr Beiträge mit dem Tag

Accepted answers

Craig Gillgrass

Ted,

This is by design. Once a dataset is given 10.1 specific functionality; such as enabling Editor Tracking, 10.0 clients can no longer open that dataset; as the 10.0 client has no knowledge of the 10.1 specific functionality.

So, if you want to enable Editor Tracking, all clients accessing the data need to be 10.1 clients.

Craig

All comments

TedCronin

We upgraded our clients to 10.1, so the relationship class lag does not exisit anymore. We still do see issues with Annotation inside of the GDB though, so perhaps that can be logged. Our current approach is to use Feature cache, but we are seeing feature cache with anno at 10.1 is equal in speed to anno with no cache at 10.0 before we enabled editor tracking. After enabling editor tracking the performance on 10 clients was really slow, too slow. Basically the two operations are what pushed us forward to 10.1 clients sooner than expected. 😞

Craig Gillgrass

Another more serious issue, is after enabling editor tracking on a 10 sde database (then disabling it), the 10 access speeds have slowed to a crawl. We started on 10.1 updates because of the issue. 10 minutes to select a record and have it show up in the Attributes window. When relationship classes are in place, the table fields have a serious lag time. Editing Anno has slowed to a crawl.

Ted, we have not seen this issue and I can't reproduce it. Can I ask you to contact Tech Support and open an incident so they can trouble shoot it and try and get a repro case for us to look at?

Craig Gillgrass

What doesn't make sense is where 10.0 and 10 SP1, support editor tracking , and SP2, SP3, SP4, and SP5 don't support editor tracking.

Ted, to clarify, 10.0 Final and 10.0 SP1 do not support Editor Tracking. We added checks starting at SP2 to look for datasets with new functionality to prevent users from incorrectly opening them with an older release where the new functionality was not supported which could lead to data loss/corruption.

TedCronin

Another more serious issue, is after enabling editor tracking on a 10 sde database (then disabling it), the 10 access speeds have slowed to a crawl. We started on 10.1 updates because of the issue. 10 minutes to select a record and have it show up in the Attributes window. When relationship classes are in place, the table fields have a serious lag time. Editing Anno has slowed to a crawl.

TedCronin

This is what I figured out, thanks Craig. Makes total sense now...:)

What doesn't make sense is where 10.0 and 10 SP1, support editor tracking , and SP2, SP3, SP4, and SP5 don't support editor tracking.

TedCronin

This is what I figured out, thanks Craig. Makes total sense now...:)

Craig Gillgrass

TedCronin

Disable fixes the issue.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.