Will there be a new version of this for ArcGIS 10.1?
Or better yet, make it part of core.
Chris, Brian:Regarding these comments: Actually, almost all of the GDBT geodatabase administrative functionality was added to core ArcGIS Desktop in 10.1. Please review this help topic,What's new for geodatabases in ArcGIS 10.1(look under the section titled New ArcGIS tools to administer enterprise geodatabases)The only thing missing from the GDBT is the "state tree viewer" functionality.Hope this helps,
Hello Derek, I've been answering this question at your and others' request in other forum threads for several years now. I am still seeing requests from users in all these threads asking for the return of the state lineage tree.
Actually, if one is lucky enough to be using a machine that had previously had 10.0 installed on it, it is still available. I am grateful to have a machine with 10.3 that retains its ability to view the state tree diagram. As new folks learn ArcSDE who have never seen this tool, they simply do not know what they are missing, but those of us who has used it, know the tables and lists in the new admin UI do not convey the same information.
The state tree/versioning lineage diagram is the best way to convey the relationships between versions. Even esri-sponsored writings, such as bug reports know this, and use a form of it in conveying information related to ArcSDE versioning. Please empower us customers by letting us know what is the most effective way to bring back an effective and powerful troubleshooting, monitoring, and teaching tool. Thanks, Clara
Clara You can check this:
Using our favourite GDBT toolset with Desktop 10.1 or later release
Good to hear from you again Clara and apologies for the late reply. I was really busy with the Esri UC last week in San Diego and am trying to catch up on emails this week.
And it looks like Asrujit provided a good workaround for you, where you can enable the GDBT functionality within a more recent ArcGIS Desktop release. Which is great - thanks Asrujit!
Hope this finds you well,
What I--and it appears many others--want from GDBT is the state lineage tree. Quite honestly, there were few other tools in GDBT that I actually used beyond the tree. As Clara stated, the visual representation makes it easy for newbies and experts alike to understand relationships between all of your versions.
The number of GDBT downloads should indicate to esri that it is an important tool for its customers. While you are correct that many (most?) of the tools are now in core, it appears that esri convened the wrong focus group when determining which functionality out of GDBT was most important to users.
While I applaud Asrujit for providing a workaround, that is precisely what we should not need to be doing 2 major releases beyond 10.1 when users brought the issue to esri's attention.
Esri, set aside your story map playtime for two seconds and make the state lineage tree part of core! Then we won't need to deal with a workaround.
Pretty much says it...
Needs to be part of core.
Hey Derek, glad to hear from you and the UC sounded like it went really, really well. I appreciate your and now also Asrujit's workarounds, but here's the thing: I work in an agency which primarily does GIS work in a citrix environment.
As you might have guessed, we have no access to install workarounds on agency blades in a remote datacenter. As for those of us who have installed arcgis on a local machine, getting access to edit registry settings is, well, not common. Sorry to say, if it takes this many workarounds, it's just not going to happen. If there's anything that could be done that doesn't require so many workarounds - like an install file, that would be simplest, wouldn't it?
Simplistic as ever,
Hey thanks Derek Law I know you're onto other things besides ArcSDE, but I checked ArcGIS Ideas (your post above), and found 6 separate threads there related to the versioning state lineage tree diagram, and can't even find (in the new system) my own forum responses to ESRI's question about how we use the GDBT. I had posted those responses in the past on request.
Here's my point: all of our feedback and requests are scattered all over the place, resulting in the appearance that this is coming from a half dozen fringe users. I was at the noontime meeting at the UC several years ago when the ESRI development panel was very clear that it was not interested in supporting the state tree diagram, and I can tell you there were more than a half dozen people in the room.
Can you or someone on the ESRI end with any interest in the GDBT and state tree diagram Asrujit Sengupta help us consolidate that feedback into one place so that our request can be viewed as one request and given its fair weight?
> ... all of our feedback and requests are scattered all over the place, resulting in the appearance that this is coming from a half dozen fringe users. ... Can you or someone on the ESRI end with any interest in the GDBT and state tree diagram help us consolidate that feedback into one place so that our request can be viewed as one request and given its fair weight?
I just checked the Ideas site and I see your point. Yes, I will coordinate getting the various separate ideas integrated into a single/unified idea - to more accurately reflect the user interest in the state tree viewer functionality.
I will update this thread when this has been done.
FYI, we've aggregated the GDBT-related ideas on the Ideas site into a single idea and marked it as implemented.
Release the GDBT for ArcGIS 10
With the exception of the State Tree viewer functionality, which had 2 separate ideas posted; which have now been combined into a single idea,
State Tree Diagram for 10.1 and above
Thanks for bringing this to my attention.
Hey Derek, that's awesome, I thank you for taking the time. A chance for a fair hearing is the main thing I've been wanting to see. Now, the ball is in our court, right? Chris Quick Brian Oevermann Paul Medley Tim Dine Joshua Bixby.
Thank you for your help, Derek
I think the ball is still in Esri's court. The community of users has already done its part by creating enhancement requests, logging ideas, and promoting those ideas. The community has played by the rules laid out by Esri, now it is their turn to make a decision one way or the other.
Hey yeah, I have posted and answered the question of how I use the GDBT and why I care about the versioning lineage diagram many times and in several places, so I very much understand the sentiment, but the request is all in one place now, and was not before this.
Derek spent the time to do that for us, which I appreciate, so I will at least try this venue, and a positive vote will only take a second. If we have better options, I'm all ears, give me a call?
I am going to try to embed a JSFiddle frame here, not sure it will work so I might be deleting this comment later. Embedding the frame didn't work, updating with link to JSFiddle instead.
A couple of comments:
I must admit, I am a complete hack when in comes to JS, which is why I am convinced that Esri really isn't interested in providing this functionality. If a novice with 2 open-source JS libraries and half of day of free time can get a state tree diagram that is in the ballpark, how hard can it be for a professional developer to bang out this functionality in some way, shape, or form.
Wow, thanks for taking a stab at that! I'm not at all distracted by swaying branches, we're all tree people in my line of work, which includes swaying branches, eh? It took me a minute to get the hang of it (lineages pointing upwards, for example) but it totally works for me, once I got over that.
I noticed another difference: at state 1871 in your example, the sync replica is showing. With all these use of 'create local copy of a feature service for editing' we need more ways to keep track of what is happening with versions and replicas. Thanks again for taking the time to do this!
Sorry to bring up an old thread but I was wondering what the SQL query of the states or state lineages table you ran against the GDB was to generate the WIL_sde_states.txt parse file? Thanks!
We use Oracle user-schema geodatabases, so you have to define the schema geodatabase of interest. My SQL file I use contains the following:
SET ECHO OFFSET FEEDBACK OFFSET LINESIZE 240SET PAGESIZE 1500SET TRIMSPOOL ONCOLUMN state FORMAT a10 HEADING 'STATE'COLUMN parent FORMAT a10 HEADING 'PARENT'COLUMN version FORMAT a50 HEADING 'VERSION'COLUMN lineage FORMAT a10 HEADING 'LINEAGE'DEFINE SDE = (name of user-schema geodatabase)SELECT TO_CHAR(st.state_id) AS state ,TO_CHAR(st.parent_state_id) AS parent ,vr.name AS version ,TO_CHAR(st.lineage_name) AS lineage from &SDE..states st LEFT JOIN &SDE..versions vr ON st.state_id = vr.state_id ORDER BY st.state_id;
For all those looking to use the GDBT with the recent releases of ArcGIS Desktop:
Retrieving data ...