Welcome to ESRI Blogs

Geodatabase Toolset for ArcCatalog - Free Download

The Geodatabase Toolset (GDBT) for ArcCatalog is now available for 9.3 and 9.3.1. Download the toolset for free off of the ESRI products page.

The GDBT is an unsupported extension to ArcGIS Desktop which provides a collection of tools that you can use to troubleshoot, monitor, and investigate ArcSDE geodatabases.The GDBT works with geodatabases stored on SQL Server, Oracle, Informix, DB2, or PostgreSQL databases. It provides a wide variety of information including:

  • The total number of rows in the add and delete tables
  • Users connected to the geodatabase and locked schemas
  • A graphic of the state tree lineage
  • Detailed information of a features class spatial index
  • Parent-child relationships between versions for version management
  • Table and Index Statistics for geodatabase stored in an Oracle database

After you download and install the GDBT you can access a help file to learn more about the toolset. It can be found in Start > All Programs > Geodatabase Toolset > Geodatabase Toolset User Guide.

There is also a support forum available for interacting with other GDBT users.

Note: The GDBT is an "unsupported" extension so ESRI Technical Support is not available for the toolset.

Published Monday, September 21, 2009 10:57 AM by JonMurphy
Filed under: , ,

Comments

# re: Geodatabase Toolset for ArcCatalog - Free Download

Couple comments - Do not install with ArcCatalog open(duh).  It will not work, and you will have to uninstall and reinstall.  

The database permissions on the account you connect with control how much information is shown.  

User Information - would be nice to be able to boot users from here instead of having to go to management studio or command line.  

Edit Information - There seems to be a bug here, as no values are ever placed in the Add / Delete / Total Change cells.  It does accurately identify what feature classes are versioned.  That is the feature I wanted most, and it doesnt work properly :(

Statistics & Indexes - Why oracle only?  SQLServer has those too.  

Great idea, thank you for putting this out!

Tuesday, September 22, 2009 3:10 PM by royjackson

# re: Geodatabase Toolset for ArcCatalog - Free Download

Comment to my comment - if you connect as the table owner, you can see the edit counts.  I wonder what permission setting is needed to allow privileges to an account - seems like SA should have all permissions needed.  

General permissions questions lurk in my brain on how this all works

Tuesday, September 22, 2009 3:19 PM by royjackson

# re: Geodatabase Toolset for ArcCatalog - Free Download

I talked to John Meza who developed the tool, and he had the following responses to your comments:

1.Couple comments - Do not install with ArcCatalog open(duh).  It will not work, and you will have to uninstall and reinstall.

<John> no comment.

2.The database permissions on the account you connect with control how much information is shown.

<John> yes.

3.User Information - would be nice to be able to boot users from here instead of having to go to management studio or command line.

<John> As in kill a users connection? In earlier versions we had that capability but removed thinking it was unused. Plan to bring it back at 9.4.

4.Edit Information - There seems to be a bug here, as no values are ever placed in the Add / Delete / Total Change cells.  It does accurately identify what feature classes are versioned.  That is the feature I wanted most, and it doesnt work properly :(

<J> I agree the sqlserver sa should have permissions.  

This is the code:

 If Len(strTableName) > 0 Then

   Set pTable = pFeatWksp.OpenTable(strTableName)

   If Not pTable Is Nothing Then

     lngAddCnt = pTable.RowCount(Nothing)

     gridMain.Text = CStr(lngAddCnt)

   End If

 End If

So it doesn’t do a sql query, but gets the row count from the A and D table. That’s it!

5.Statistics & Indexes - Why oracle only?  SQLServer has those too.  

<John> Yes, but statistics are automatically updated in sqlserver based on a algorithim (time, useage, etc.) so it wasn’t a big concern in sqlserver. When this was developed Oracle didn’t have that capability and it was a common performance issue that could be easily corrected by maintaining table and index statistics. That may have changed with: 11g incremental global statistics, copy table stats procedure, 10g had dbms_stats.gather_schema_stats with the option "GATHER AUTO".

Also, I tried to get the sqlserver stats early on and it’s a big pain, and susceptible to many permission problems.

I think it’s useful for Oracle and not that useful for SqlServer, but that may be incorrect.

Hope this helps,

Jonathan

Wednesday, September 23, 2009 11:24 AM by JonMurphy
Anonymous comments are disabled