Latest Contributions by TinaMorgan1

Hi Tim, thank you for your comment.  Just a heads up, performance issues are usually very complex and require loads of testing/comparison cases to understand root causes.  The true cause of performance could be due to any one (or more) pieces in your set up.  This feed has gotten pretty specific to users who believe they have narrowed down their performance issues to a particular bug, based on previous tests and comparison cases.  If you have done such tests and comparison cases you may always include them in your comments.  The best route to effectively triage performance issues will be to call Esri Support so they may guide you in which tests will be most efficient to narrow down the issue. Esri Support # 888-377-4575 to create a new case. ... View more

if there is a record in the versions table that has a state_id of 0 then that means that version was created off of its parent when it too was at state zero, AND that no one has ever connected to that version and made edits within it.  Basically you can delete it, as it has never been used. Feature classes can be registered as versioned and that has no effect on how many versions you actually have.  You may register every feature class in your geodatabase as versioned, but never create any transactional versions to edit within (other than DEFAULT which will always be there). If there are edits in the a and d tables then that data has not been compressed.  Period.  If you ran a geodatabase compress and STILL see records in the a and d tables, then that means those edits are still being referenced by something, for example an open edit session or a version that has not been reconciled and posted. ... View more

Really nice!  I am going to share this with users. ... View more

So being picky on semantics here, versions do not hold data.  So the default version doesn't 'hold versioned data'.  It is simply a view that combines edits made within that version.  The view uses the state_id which can be traced up the versions lineage (state_lineages) all the way up to the base table.  Edits (record updates, inserts and deletes) are what hold states, and those edits must be made within a version so the version state_id only represents that. So when you compress a geodatabase those edits (with state ids) are pushed from the delta tables into the base table.  That's where the bulk of the action happens.  The other tables (versions, lineages, etc) are for used to implement Esri's multi-user geodatabase functionality.   (first what kind of database are you using?  SQL Server, oracle, ??)  You can go into your database tables and you should see some tables like a## and d##.  These are your delta tables.  The number corresponds to the registration_id of the table_registry table.  That's where your edits are in a versioned database.  When you compress the geodatabase those a and d tables are truncated, and the edits are pushed into the base table. This is an old article, but a good one... Versioned tables in a geodatabase in Oracle  ... View more

Right, my understanding of the question is that they are trying to find out which delta tables have records still in them, in other words, which feature class's delta tables still contain records that can be compressed to the base table.   I am not sure of a way to check the record count of delta tables in ArcCatalog, and the way I would do this would be to just query the database with SQL. Depending on what your data looks like, you may get something like this by making a database view on the base table.  Since Esri applications will be the base table + the delta tables, making a view on the base table alone could give you an idea of the differences. ... View more

Have you ran Verify Connectivity or Repair Connectivity,  on your network?  You may also run Verify Feature Network Geometry to check for issues with the network geometry. About Verify Network tools and commands—Help | ArcGIS Desktop  ... View more

If I understand correctly, you see an error when you attempt to edit polygon records from your feature class.  Could you include the exact error you see when attempting to delete the records? ... View more

Is your buffer area large enough to include the entire area of your polygons?  I wonder if any portion of the polygon lies outside of the buffer if it is being discluded. The script filters out features not completely within. Filter out features that are not actually in buffer, since we got all points in the buffer's bounding box ... View more

What version ArcDesktop are you using?  What version is the geodatabase (If you are using ArcDesktop 10.1 or higher you can get this info by right clicking the .sde connection in ArcCatalog-> Properties-> General tab, there is an upgrade status section that tells you the version of gdb) If possible to test, are you able to use single use licenses without issue (i.e. could this be due to License Manager handing out concurrent use licenses?) -TM ... View more

Hi JAY! Right, it sounds like someone had an SDEBINARY feature class in SQL Server then just gave him the base, s and f tables (the f table will have a points column with a hex data). If that is the case, then there are better methods to send this data to you in the future.   ... View more

Is this data ready to be a sync enabled feature service? To use the sync capability, all the data in the feature service must be from an enterprise geodatabase. Also, you must prepare the data so it can be used offline and, if required, synchronized through the feature service when you have connectivity. The data you use in a sync-enabled feature service can be either nonversioned with archiving enabled or, if your organization's data or workflows require it, the data can be versioned. Be aware that you can only enable the sync capability when all the data in the map is configured exactly the same; you cannot have a mix of versioned and nonversioned data. Prepare data for offline use—Documentation | ArcGIS Enterprise  ... View more

There is no installation for ArcSDE starting at 10.1.   ... View more

I'm sorry you encountered that issue.  Great work researching and testing though!   ... View more