Latest Contributions by DavidHoy

Hi Evan, I dont know of a comparison page, but... There are a lot more ST_ functions provided by PostGIS than there are with the sde.st_ function set. The ones with common names serve the same purpose (syntax may be different) The Esri reference set is: ST_Geometry SQL function reference  and https://desktop.arcgis.com/en/arcmap/latest/manage-data/using-sql-with-gdbs/a-quick-tour-of-sql-functions-used-with-st-geometry.htm PostGIS equivalent is: https://postgis.net/docs/reference.html hope this is somewhat useful ... View more

Hi @BenjaminBlackshear  There is an excellent post on this topic here that is well worth a read. https://community.esri.com/community/implementing-arcgis/blog/2020/04/30/planning-load-balancer-configuration-for-highly-available-arcgis-enterprise In a nutshell, you need a HealthCheck for each target (VIP) endpoint configured with the Load Balancer. If there are Web Adaptors, you only need to check that the Web Adaptors are available.  In your setup, with Portal & Server Web Adaptors on the same machine, I guess you have LB set to share all incoming requests to one "target group" with two Machines. In that case, you only really need a tcp availability health check for the Web Server hosting the two Web Adaptors. You do not need to use the Portal or Server healthCheck REST endpoints. (The Web Adaptors use these behind the scenes). If you use separate targets for the portal and server Web Adaptors, you could try just simple html checks for the healthCheck addresses. But... this only tells the Load Balancer that the Web Adaptor on that machine is working and that at least one of the portal/server sites is responding ok. The healthCheck endpoints are not always super fast to respond, so allow some more time and a few more retries than you may expect (as per the blog article) Hope this helps ... View more

The log says it took 1 min 24 sec to run the serversite export on the "gis" server site, and then failed when webgisdr tried to compress/copy the output file to the "shared_location". In parallel, the portal backup process ran for 9 min 2 sec and then failed when webgisdr tried to compress/copy the output file to a different folder in the same "shared_location". Possible reasons: the fileserver hosting the "shared_location" ran out of disk space. as webgisdr deletes all the temp output when it fails - it can be hard to see this when looking at the file server after the event. the service account running portal and "gis" server for some reason no longer has read/write access to the shared_location are all your machines using the same domain service account? or do they each run a local service account? as you say the process has been running successfully in the past, it would only be an issue if file share permissions have been changed the file server has some hardware issue - bad sectors or a faulty USB connection but if you are seeing the error appear in the webgisdr log at the same place each day, it seems unlikely to be an intermittent hardware problem you may wish check this site for some ideas (I just googled this up)  https://www.diskgenius.com/how-to/device-attached-to-the-system-is-not-functioning.php      ... View more

There was a further clarification update to the Patch download page that explains why only one Web Adaptor appears to have been patched. https://support.esri.com/en/Products/Enterprise/arcgis-web-adaptor/arcgis-web-adaptor-iis/10-8-1#downloads?id=7855 Important Note: A single installation of this ArcGIS Web Adaptor (IIS) 10.8.1 Stability Patch will update all ArcGIS Web Adaptors configured on a machine; no additional installation or configuration is needed for multiple web adaptors on a machine. You will observe some limitations with the tools used for finding and notifying of patches. The PatchFinder.exe is currently limited to only showing one web adaptor even though the patch has been applied to all web adaptors. The Patch Notification tool does not currently support showing patch notifications for the ArcGIS Web Adaptor.   ... View more

Andrew, what you say may be true if you are using SQL to create new tables, but ArcGIS enforces a rule that only a schema with the same name as the connected user may be used.  See https://desktop.arcgis.com/en/arcmap/latest/manage-data/gdbs-in-sql-server/add-users-sqlserver.htm  "Database users who will create tables and feature classes must have privileges necessary to create these objects in the database, and they must have a schema in which they can create them. When using ArcGIS, that schema must have the same name as the database user." If you try to add a new feature class and teh default schema name is not the user's name, you will get an error message something like DavidHoy_0-1621558978810.png   ... View more

Hi YeshiWangChuk, what you are seeing is a field that has an associated Domain, but some of the actual data values in your table are not valid codes for the Domain. ArcGIS cannot find a Description, so just shows the code value. It is a bit odd, if you have used any of the techniques described above to copy data from Enterprise Geodatabase to File Geodatabase, the associated domains would have come with it. Is it possible some other edits have happened after transfer? - or do you see the same behaviour when you look at the class still in the Enterprise Geodatabase (using ArcGIS tools)? ... View more

Andrew, to expand on Bill's answer. You cannot create new classes in a schema that is not the logged in user's own. I.e. User named mydomain\user1 cannot create feature class (table) in the "dataowner" schema. So, if you want to use specific schema (and this is a good data organisation practice), as Bill says, you need to use Database Authentication, create Logins and add them to the Database with sufficient privileges to create content (db_owner would be OTT, these database users only need  CREATE TABLE CREATE PROCEDURE CREATE VIEW Then, create database connection files for each of these Users, use these connections when creating new classes (or updating their structure/indexing). The new tables will automatically be created within the schema that has the same name as the login. Once created, you can assign required privileges to the new classes for Roles in the database (that may be associated with AD Groups) That way, your OS login can be allowed to see/edit the datasets that are appropriate for them. The use of schema in this way helps to groups data that has similar source or purpose. ... View more