topic Re: Editor Tracking 10.1 Issues in Data Management Questions

Editor Tracking 10.1 Issues

TedCronin — Wed, 27 Jun 2012 16:12:17 GMT

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

Re: Editor Tracking 10.1 Issues

TedCronin — Wed, 27 Jun 2012 18:37:53 GMT

Disable fixes the issue.

Re: Editor Tracking 10.1 Issues

CraigGillgrass — Mon, 02 Jul 2012 16:27:53 GMT

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

Re: Editor Tracking 10.1 Issues

TedCronin — Mon, 09 Jul 2012 17:39:01 GMT

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

Re: Editor Tracking 10.1 Issues

TedCronin — Wed, 11 Jul 2012 14:59:58 GMT

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.

Re: Editor Tracking 10.1 Issues

TedCronin — Wed, 11 Jul 2012 19:50:05 GMT

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.

Re: Editor Tracking 10.1 Issues

CraigGillgrass — Thu, 12 Jul 2012 12:59:11 GMT

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.

Re: Editor Tracking 10.1 Issues

CraigGillgrass — Thu, 12 Jul 2012 13:00:14 GMT

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?

Re: Editor Tracking 10.1 Issues

TedCronin — Thu, 12 Jul 2012 23:17:13 GMT

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. 😞