Latest Contributions by VinceAngelo

Best practice would be to use a commonly supported database (e.g. SQL Server 2012) for "release too far" migrations, then once upgraded (to 10.4.1), upgrade to the final RDBMS (2016).  Once the gulf between releases doesn't have any shared supported environments, you need to consider whether a "export to FGDB, import from FGDB" might be most appropriate (lest you need to iterate upgrades and platforms to reach the goal).  In-situ upgrades give me agita, especially from a non-terminal release (10.2.1 vice 10.2.2) over intervening terminal releases (past 10.3.1), since the potential for upgrade failure increases when the test cases are fewer and farther between. Where possible, I prefer to review properties which can't be changed (more efficient spatial reference, data load in spatial index order,...), and evaluate whether an export/import upgrade is appropriate. - V ... View more

Hey, I haven't created more than three or four, maybe five new standards. Well, unless you count... Let's say, no more than seven. - V ... View more

Oh, great, now I'm the keeper of the standards tontine of blame?  That will help me sleep at night. - V ... View more

Cross-posted to GIS Stack Exchange (though no responses there yet) - V ... View more

I want to debug code that contains: with arcpy.da.SearchCursor(featureclassname, featureclassfieldnames) as antidisestablishmentarianisms:     for antidisestablishmentarianism in antidisestablishmentarianisms:         blah - V ... View more

One BILLION vertices?! Yeah, that would slow down most apps, even if hundreds of millions of them were removed for being duplicate at the precision of the spatial reference. In fact, that likely qualifies as a (self-inflicted) denial-of-service attack. - V ... View more

Both are valid. The first is just a naming preference for working with list comprehensions. In the absence of thorough documentation, a coherent naming policy can self-document many a script. There often times when a code cascade raises conflicts with standard naming, at which point you need to do the best you can. Remember: The nice thing about standards is that you have so many to choose from. - V ... View more

The purpose of the clause array is to prepend and postpend to the SQL statement.  The postpend is used for ORDER BY and GROUP BY. If you add inappropriate content, you will may get an error (depending on what the original SQL would have been). That's less bug than undefined behavior. - V ... View more

What is the version of the enterprise geodatabase which you are manipulating? What is the release of the admin binaries? I haven't needed to use sdelayer -o delete in over a decade, possibly two, so I can't help but wonder why you need to use this (and fear for the integrity of your geodatabase). - V ... View more

To clarify, the result of a to_char(datecol,'YYYY-MM-DD') is a text field (which is interpreted as a CLOB column, and caused an issue with ArcGIS 10.5 on PostgreSQL).  The  syntax to cast the string conversion would look like: SELECT idcol,cast(to_char(datecol,'YYYY-MM-DD') as varchar(10)) as datecol_str FROM  mytable‍‍‍‍‍‍‍‍ Make sure the VARCHAR width is wide enough to hold the formatted date! - V ... View more

There seems to be some pieces missing from your code sample.  arcpy.da.InsertCursor creates rows, and arcpy.da.UpdateCursor changes specific rows. You seem to be trying to use UpdateCursor to insert rows. If you really want to update rows, then you should be applying a where_clause to limit the interaction to the affected rows. Please remember to specify the exact version of software in use and what the data source(s) is/are (file geodatabase has different SQL options than a real database). - V ... View more

This is less a follow-up than a completely new question, but yes, extensions are licensed using the same model as the base software -- 8 CPU cores = two 4-core licenses. This could be addressed to your marketing/sales rep or a contracts rep if you need further clarification (legal stuff is better asked of corporate representatives than random users on GeoNet).  - V ... View more

Note that there's a difference between "Run" and "Runs well", and a difference between "Runs well with trivial input" and "Runs well with massive input."  The RAM in the computer may have as significant impact on the viability of the platform as the CPU (and disk performance isn't too far behind).  It's difficult to predict platform suitability for any purpose without specific details about the configured host and workload. - V ... View more

Anything can get corrupted, especially when you replace an existing with a new one.  The mixed release levels probably isn't helping.  Have you tried using a 10.5 client? ... View more

It's important to keep in mind that enterprise geodatabases contain tables, not files, and that some of the usual practices which are casual about deletion and re-population in file-based storage mechanisms would be better off being redesigned to be less brutal on table elimination and creation in databases. For example, if the shapefile schema isn't changing with each release, using Truncate Table and Append would be less burdensome on the database, and would have the side effect of not needing an explicit delete or initializing the environment to permit target overwrite. - V ... View more