Latest Contributions by RyanKoschatzky

A few strategies we have used, while not at Pro we will still most likely do a scheduled quarterly downtime. In traditional versioning we went to state zero but when we also would make database changes and take a data cut. That would be time period we could schedule such work. Another method, with 7 lrs editors and 15 event editors in the system there can be lots of different locks in the system. We would break down the work by smaller boundary area where people are not working like a county or a collection of counties.  That can handle 95% or more of the work effort. Easy enough to have the business unit get out of their own way for an event update. Our lrs editors are posting every few days when complete with work and easy enough to work around a few exclude routes and updating the rest of county until a route lock is removed or a little coordination on needing a few minutes to update has work effectively in the past. Instead of allowing the tool to grab a lock to edit, I would grab a route lock or an event lock at minimum first than process the action on that same selection. That might get around the 99999 issues. If updating monthly, I would think about pulling out that field out of that feature class to another feature class to make doing append events a simpler effort. You can do the work outside R&H and add later. Just a thought. I am sure there is some other creative solutions to update data changing that often.  ... View more