Latest Contributions by VinceAngelo

It's not possible (or wise) to enforce unique constrains on versioned feature classes, since edits can result in duplicate attributes in different versions (causing conflicts in the ADDs table). As a rule, you should choose whether you want the geodatabase model to control a table or not, and register only those tables over which you are willing to relinquish control. Piecemeal management of registered tables causes most of the anguish tossed into the laps of my colleagues in Tech Support. I recommend you don't make their new year a difficult one. - V ... View more

There are certainly some cases where you do want to only use ArcGIS tools for index construction, mostly involving versioning or archiving.  In those cases database tools are unable to discern what other tables need the same indexes, and performance could be harmed as a result.  Using database tools takes a large burden on your own shoulders to do the right thing, so the documentation isn't going to recommend you place yourself in that situation. - V ... View more

It would help if you specified which RDBMS you are using, the version of that RDBMS server, and the version of the client libraries being used (both on your host and others). Application crashes are extreme events; they shouldn't occur, and if they do it's often due to incompatible DLLs.  -V ... View more

There are very few reasons to ever connect using ArcGIS as SYSTEM (it probably qualifies as a Worst Practice). This is especially true if the number of objects in the database is large, since connection time closely correlates to the number of objects visible by the user (and SYSTEM can see everything, including the thousands of demo/sample tables that should not reside in any production server). - V ... View more

This is probably something to discuss directly with Tech Support.  The alternative is to post a new question, giving lots of details on the exact OS and software, the exact PATH contents, and the exact procedure to produce the error. - V ... View more

ArcGIS 10.5.1 is the current release. I would recommend ArcGIS 10.5.1 over 10.5.0 for immediate use. Pre-release builds are not supported for upgrade to final, so pre-release is not comparable to any final release in terms of deployment. 10.6pr is great to practice for 10.6 upgrade, but you have to be willing to walk away from any data which has been migrated. - V ... View more

Any Python will do, though if you have more than the default urllib it will likely be easier. - V ... View more

There are code samples for using Python to call the REST API.  You need to get a token first. I don't have my source handy at the moment, but it isn't more than a score or two lines of actual code.  -V ... View more

I have no concern whatsoever about VM use with ArcGIS 10.2.2 or higher (since I've used that extensively). Given that it's extremely easy to write memory leaks with ArcObjects, my concern is with your code. - V ... View more

I'm not convinced that the application failure is even ArcObjects-related. This could be a COM failure itself (ancient components are written against ancient libraries, after all). There is no way, short of submitting your code for review, to tell what might be wrong.  If you can generate a short code sample which generates the same error using ArcObjects 10.3.1, you can submit it, along with a detailed description of the inputs (type, feature count, and mean vertex count), to Tech Support. There really isn't any way for the good folk of GeoNet to help you, given the information provided. - V ... View more

ArcGIS 10.1 was released June 11, 2012.  The SP1 service pack was issued October 2012, and the most recent patch to that service pack dates to July 2014. ArcGIS 10.1 will enter Retired support status in six weeks (Jan 2018).  Even if I were to accept the "Esri releases updates too fast" argument (this is the first time I've ever heard it), I'd have to question the wisdom of letting a development project lapse five years (and four, soon to be five, major releases) behind the current build. Staying three months behind is wise. Waiting for the x.y.1 release is prudent. Staying fifteen months behind is conservative (and somewhat tricky, since some products start to lose support status at eighteen months). Falling sixty months behind is risky from OS compatibility, database compatibility, and system security standpoints (any of which could cause the errors you're encountering). The usual route to address "memory leak"-like behavior is to apply all patches and try again.  If the tool works for over a hundred datasets at a time, then organizing batch processing to limit execution to one hundred folders at a time is your path of least resistance. - V ... View more

What exact version of ArcGIS are you using?  I don't use non-enterprise geodatabases, but I wouldn't have expected the "Database Connections\*.sde" path for the connection file to an Express database (Database Servers).  Your code's comment asserts an enterprise geodatabase, which generally locks specific tables. I would guess that your edit session is superseding the table lock, so you can probably comment out the entire with block for purposes of testing. ... View more