Latest Contributions by VinceAngelo

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

According to the 10.8.1 doc (https://desktop.arcgis.com/en/system-requirements/latest/database-requirements-postgresql.htm), support only goes to PG 12.2+ (PG 12.4+ for Pro 2.7), so it can't be before ArcGIS 10.9. If you haven't made it all the way to PG 12.x yet, I urge you to pay close attention to the note about "WITH OIDS=True" in older databases.  That's an ugly transition, there.  Cost me about 25 hours during a four-day migration, since pgAdmin4 pg_dump corrupts the "WITH OIDS=True" in PG 11 -> PG 11 migration, too. - V ... View more

If the data all registers well, then the difference is due to string comparison on projection names, not actual coordref differences.  This is one of the few cases where clobbering the .prj is acceptable (save the old one, though, just in case). - V ... View more

You generally want a hosted feature class or Enterprise geodatabase table for dynamic tables, since multi-user access with ACID (Atomicity, Consistency, Isolation, Durability) is an intrinsic feature of RDBMS. - V ... View more

If every row has a NULL value in that column, you certainly don't want to assert a NOT NULL on the column until the table has been updated so that only valid (non-NULL) values are present. - V ... View more

You can only enforce NOT NULL on a column if the table doesn't have NULL values in that column. You'll need to fix this first. - V ... View more

The "{tablename}" and "{columnname}" and "{datatype}" need to be replaced with actual values, e.g., ALTER TABLE [EDIT_TEST] ALTER COLUMN [TEST] nvarchar({actualwidth}) NOT NULL (Yes, you need to replace "{actualwidth}" with the defined width of the column). - V ... View more

If the table is not versioned, you can use SQL to alter the column: ALTER TABLE [{tablename}] ALTER COLUMN [{columnname}] {datatype} NOT NULL You should then open the table in the Catalog view as the table owner, to make sure the properties are correct, and populate the update to the sde.sde_column_registry table. - V ... View more

Friends don't let friends use Excel for data transfer (especially large data transfer).  CSV is much less likely to be mangled. - V ... View more

Daily reboots aren't really part of best practice.  Some of my clients have monthly "hardware" restarts, and if you want to be hard-core then weekly restarts could be scheduled, but the server recycle is supposed to obviate the need for *any* reboots. - V ... View more

Just because midnight is the default service restart time doesn't mean it needs to *stay* the service restart time. I ran a script to assign restart times in round-robin fashion with an interval 15 minutes between of hours of  0015-0445. - V ... View more

I'm getting HTTPS errors on your file links. If you put the parameters in the question as text, then no one would need to download an image for the definition of "crazy." Yes, spatial reference tolerances can have an impact on the compression algorithm used to store geometry, but only when using Esri's ST_GEOMETRY storage (you haven't specified the RDBMS or geometry storage type, either). Yes, correcting the feature dataset spatial reference generally requires a complete reload of all the feature classes, and replacing a feature class spatial reference generally requires recreating and reloading the feature class. - V ... View more

Oh, dear.  It's not very fair to assign this task to a non-DBA.  Database transition is the time when inexperience can introduce inefficiencies which are much harder to eliminate down the line.   ORDER BY is the database's "sort on" directive. It's a row thing not a column thing (though reorganizing columns that have been added in dribs and drabs is a good example of a low-cost update during transition). Spatial fragmentation occurs when data is added to a table in an unordered fashion, such that, when a basic draw request at full extent is made, the features seem to draw in random order. Spatial defragmentation is the process of organizing row order such that draw requests result in a systematic fill, such that, when the extent is at a much more restrictive scale, the features that are drawn are from at most several nearby clusters of rows (reading fewer rows to meet a query request means a faster draw time, and less space consumed in the cache for any one query, which means other queries can also be faster).  In extreme cases, spatial defragmentation of, say, 10 million lighting strike records, can result in simple query times dropping from minutes to sub-second. In regular use, it might mean the difference between 700-800 and 200-300 milliseconds during a JOIN -- still significant, but you're much less likely to get rose petals scattered before you and cheering crowds forming spontaneously on your way back to your car. - V ... View more

Keeping a database backup isn't going to be of much use if you won't have a SQL Server instance into which to restore it (sort of like making floppy backups before taking delivery of a new ultra-thin laptop). I usually have the SQL used to create my tables available, so I've been able to create a new empty template in the PG database, then use SQL to optimize the table organization for spatial index order, or at least somewhat spatially defragmented (e.g., counties left to right within states in UTM Zone order), before re-registering with the geodatabase. If you're going to have to migrate, you might as well get some optimization out of the deal. Sometimes you can create views for the data export to add an optimal ORDER BY when loading the FGDB out of the database, other times it easier to FeatureClassToFeatureClass into a staging schema, then use INSERT INTO finalschema.table1( {fieldlist}) SELECT {fieldlist} FROM tempschema.table1 ORDER BY sort_seq_added_earlier Integrating as many other moderately costly updates into your design as the migration effort can support will manifest in reduced runtime in the new instance.  Conversely, not taking the time to optimize can hobble the performance of the new environment indefinitely. - V ... View more