Latest Contributions by George_Thompson

You would need to compare to the SQL trace to the SDE intercept to see what SQL Server is doing at the same time. It could be on the SQL side and the ArcGIS client is "waiting" for something back. It would be best to work with technical support on this issue. They can help you dive deeper into the issue. ... View more

You can run a SQL trace in SQL Server and look at all the operations being completed during the append process. This will tell you where the time is spent. You can also do an SDEINTERCEPT (https://support.esri.com/en/technical-article/000014807) on ArcGIS Pro at the same time which can be used to compare where the time is spent: client (ArcGIS Pro) or SQL Server. I wonder if some of the time is updating indexes, which is not an ArcGIS "task". If you run the GP tool (not in model builder) does it have different run times?   ... View more

Hi Jeremy - I have directly worked with Zarr data yet, I do have large clients testing / using Zarr data now. I will say that there could be something in the Zarr file that Pro does not like. I have seen this with other formats. Maybe a recommendation would be to contact technical support to work with them on this. ... View more

Yep, you can create a multidimensional raster layer: https://pro.arcgis.com/en/pro-app/latest/help/analysis/image-analyst/an-overview-of-multidimensional-raster-data.htm Tool Reference: https://pro.arcgis.com/en/pro-app/latest/tool-reference/multidimension/make-multidimensional-raster-layer.htm ... View more

There are a few things I noticed and comments about them: If you move an Enterprise Geodatabase to the cloud, I would HIGHLY recommend that you put the ArcGIS clients in the cloud also. In the link you reference in your first paragraph it states this in the note. If you just need an Enterprise Geodatabase (EGDB), you can get ArcGIS Server Basic which will allow you to enable the EGDB. The limitations with Server Basic are on the publishing to server, not EGDB (as I understand it). The big item will be to have ArcGIS client with Standard / Advanced license for creation / editing the of the EGDB. I am not sure I would trust that "trickery" to work and risk corruption and / or data loss. Questions: - Why are you looking at cloud if you say "And I do not need Cloud as well because I just can use file geodatabase on shared folder. the FGDB is suffice enough to cover our needs."? - Is your organization trying to save money on storage? Based on what you have provided, I would say just stay in the current model. I do not see a benefit to move to the cloud. I could be missing something so please let me know.   ... View more

The st_geometry library can be downloaded from My Esri. ... View more

Here is some documentation on this: https://pro.arcgis.com/en/pro-app/latest/get-started/run-pro-on-a-mac.htm Hope it helps! ... View more

I wonder if it has something to do with caching within the Pro client. I think that Pro caching some of the layers information to allow more performant responses in the client. Interested to see what others say also. ... View more

I was worried about that. See the comment from @SepheFox1 below. I would guess that is what you are encountering. There is not a way around that unless they increase the export feature limit. ... View more

Have you run Check Features: https://pro.arcgis.com/en/pro-app/latest/help/data/validating-data/invalid-geometry.htm or the Export Features tool (mentioned in the screenshot you posted): https://pro.arcgis.com/en/pro-app/latest/tool-reference/conversion/export-features.htm? What is the data source of the flood hazard layer? ... View more

Here is a blog talking about SQL & Branch Versioning: https://www.esri.com/arcgis-blog/products/utility-network/electric-gas/utility-network-sql/ I would recommend against directly editing the table....... As for the size, there is an idea: https://community.esri.com/t5/data-management-ideas/trim-archive-history-tool-for-branch-versioned/idi-p/1055659 that would be to trim the table. Go over and add your use case or Kudos. Hope this helps! ... View more

As long as they are supported, they all work well. I have lots of clients using SQL Server & PostgreSQL. The main question is who will be managing the RDBMS and what are they familar with? ... View more

Like Marcelo said, it is not possible to update with SQL. As for the migration, it is safe to use. I would also highly recommend a backup before running the process. One gotcha I have seen with that tool is space: make sure that you have enough space available in the RDBMS to expand during the process. The tool basically "copies" the table in memory then does the conversion finally deleting the SDEBINARY version. I would HIGHLY RECOMMED this is done during a maintenance window to remove any locks from the tables in question. ... View more