Latest Contributions by VinceAngelo

This isn't likely to be a tiny task. These forums aren't really geared to tasks that would take an experienced developer weeks to complete. They're usually for more immediate problems which can be addressed in a paragraph or two. We can help you if you work at it and get stuck, but you'll need to come up with a plan and start to see it through. The alternative is to contract with someone to code it for you, but I usually don't get involved at that level. - V ... View more

While theoretically possible, a great deal would depend on the exact format of the file. - V ... View more

There are some times when the 'sde' login needs advanced privileges (install/upgrade on other than RDS), but other than that, there shouldn't be any problem with plain vanilla user privs. - V ... View more

Maintaining an open arcpy.ArcSDESQLExecute cursor would probably accomplish the same thing. ... View more

Poison starfish (if I can't run PostgreSQL on coconuts with vines and ferrous rocks for cores). - V ... View more

My (hazy) memory was that they were in the INFO file, and could be edited, but would be clobbered by the next BUILD or CLEAN. - V (Since 4.01/5.0-beta) ... View more

18791 days after 01-Jan-1970 isn't likely to be 19-Jan-1970; perhaps you used a converter based on milliseconds, and you need to multiply by an additional 1000? - V ... View more

The SQL looks good, though making the 'sde' login the owner isn't best practice (the 'sde' login should be treated as an administrative account, used only when absolutely necessary, and never to own geodata). - V ... View more

In ArcGIS parlance there's a difference between a "GlobalID" and a "GUID". Both utilize UUID field types, but a GlobalID is a primary key ("GlobalIDs uniquely identify a feature or table row in a geodatabase and across geodatabases."), while a GUID is a field that utilizes the native UUID datatype (possibly referencing a GlobalID in a different table). There are many ways to manifest a GlobalID as a GUID in a table, but the details vary depending on the storage types of the table sources.  If both are in a single Enterprise geodatabase instance, the UPDATE is as easy as the supporting RDBMS permits cross-table joins to be. If you're using file geodatabase or a number of different data sources, then the tools that support this are limited (but there are still multiple ways). Ironically, as good as the UUID type is for distinguishing unique records, it is large and inefficient at that task; integer types make for much more efficient storage and comparison in very-large tables. How "standalone" is your standalone table? How large are the tables (in rows)? What data source(s) are you using? What have you tried? - V ... View more

No, no, no! Don't use shapefile to transfer data between SQL databases -- It will corrupt any numeric NULLs, datetime or string data exceeding 254 width (not to mention all field names in excess of ten characters). File geodatabase was designed to support all the types likely to be found in either database.  Note that there could be reserved word issues to resolve after export but before import. - V ... View more

I've seen anecdotal evidence that PG 13.x (with PostGIS 3.1) can be used in a database connection from Desktop (as a non-geodatabase, without EnableEnterpriseGeodatabase) , but that this connection can't be registered with an ArcGIS Server 10.8.1 instance.  When the user switched to PostgreSQL 12.6, there was no difficulty registering the connection. ... View more

Shapefile is dreadful for this purpose, since it doesn't support the feature dataset container that supports networks.  File geodatabase is really your only option. - V ... View more

Legal questions like this are best asked of your lawyer, or by your lawyer to Esri's laywers. Asking strangers on the Internet is worth less than you pay for it (and does not absolve liability), but it seems that your use does not meet the "for free" criteria, and therefore such use would violate the Esri TOS. - V ... View more

You know how it works. Only Development makes promises about future development, and Support reports the supported environments. Even if I knew the plan (and I don't), it's not my place to say more than, "It ain't there yet." My problem was with a PG 11.8 to PG 11.9 transfer, where a geodatabase upgrade wasn't available, but the OID support was corrupted by the export -- pg_dump actually corrupted the geodatabase before the PG 12 support geodatabase changes could engage. - V ... View more