|
POST
|
Oh, so you were opening the Pro projects from a cloud drive.... I would anticipate that would take a while to open and populate the layers.
... View more
12-12-2023
06:52 AM
|
0
|
2
|
6552
|
|
POST
|
I would anticipate less than optional performance when connecting over VPN. The network and VPN client (scanning / encrypting / decrypting / other VPN things) is going to more than likely be the limiting factor in this. The ArcGIS clients need robust communication between the clients (Database / Pro / Enterprise). I know that there may be some people to crack open the special sauce on the VPN / Pro client performance; but in my experience, it is usually not as good as being in the same cloud / datacenter / office. We normally recommend that the Pro client is in the same datacenter / cloud region as the geodatabase; https://enterprise.arcgis.com/en/system-requirements/latest/windows/databases-in-the-cloud.htm This helps to cut down on latency / performance issues as you are experiencing. I would recommend testing having a Pro client in your Azure cloud (https://pro.arcgis.com/en/pro-app/latest/get-started/pro-on-azure-cloud.htm) and do some testing to see if the performance is better. Another option, depending on the use cases and functionality needed, would be to publish the feature classes as feature services and edit via REST services. This would improve the performance when editing on VPN connecting to your ArcGIS Enterprise deployment. Hope this helps point you in the correct direction. Let us know if you have any other questions.
... View more
12-12-2023
04:30 AM
|
0
|
4
|
6596
|
|
POST
|
What is the data source that you are updating from? I wonder is the Input has some weird schema attribute in it.
... View more
12-11-2023
07:21 AM
|
0
|
0
|
2581
|
|
POST
|
What are the errors being received? What is the RDBMS version / Enterprise Geodatabase version? How are you appending this data: GP tool, Python, etc.? I think that we will need a few more details to help with this.
... View more
12-11-2023
04:31 AM
|
0
|
5
|
2614
|
|
POST
|
The simplest way I would recommend to accomplish this the following: Recommend removing db_owner role from SDE, except for upgrade process May want to grant VIEW DEFINITION to SDE if not already done https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/privileges-sqlserver.htm Create a Database user (Not a domain account - see comment from @MarceloMarques ) with the GP tool: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/create-database-user.htm - you must use a connection that SYSADMIN server role This can be done for multiple data owners as needed For the users that will view / edit the data, I recommend using Active Directory (AD) groups so that you do not have to manage user names / passwords for each person. You just add the group in ArcGIS Pro with the correct permissions (View or Edit) If they leave your company their account is turned off and you do not have to do anything. You just need to make sure that you secure the PW to the SDE and Data Owner accounts. If a person leaves the company, it may be best practice to update the PW for those users as needed. This should prevent issues with data ownership being a "free for all" in your organization. All the "management" of the tables will be done by the data owner, to simplify administration of these tables. There may be some other ways, but this has been successful in the past. Hope this helps!
... View more
12-07-2023
07:18 AM
|
1
|
2
|
4401
|
|
POST
|
You need to connect the Enterprise Geodatabase as SDE and update the license. This message is usually when the license expires in the geodatabase. We also have a GP tool to do this: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/update-enterprise-geodatabase-license.htm This should get you going.....
... View more
12-05-2023
07:03 AM
|
1
|
0
|
1707
|
|
IDEA
|
@RusselBell have you seen the updated documentation on this: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/arcgis-field-data-types.htm#GUID-3C98DA8B-8D97-4E9F-AA34-F69C737A9871 and the new GP tool: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/migrateobjectidto64bit.htm I would review the information in the documentation before running the tool.
... View more
12-04-2023
09:21 AM
|
0
|
0
|
2917
|
|
POST
|
You can download the ArcGIS Coordinate Systems Data file from My Esri under the ArcGIS Pro 3.2 downloads page:
... View more
12-04-2023
07:06 AM
|
0
|
2
|
3522
|
|
POST
|
I am not sure of a specific recommendation. It may be best to contact Technical Support and work with an analyst on this issue.
... View more
12-01-2023
04:50 AM
|
0
|
0
|
12626
|
|
POST
|
There are pros / cons to both ways. I would say that file geodatabase (fGDB) is not a bad way for storing that data for archive. The bigger thing would be related to the data security, if this is being discussed for the archived data I would lean towards the Enterprise Geodatabase (EGDB). I can also say that many DBA's do not like to store data in the EGDB that is not being used, as it "cost" more to house it in the RDBMS and maintain. I will be interested to hear others thoughts......
... View more
11-29-2023
06:56 AM
|
3
|
0
|
3241
|
|
POST
|
Are you using the same connection information UN / PW in Pro as QGIS? In my connections with PostgreSQL, I can see what the user has access to. If you have user with (superuser) then they can see many other items that some could not.
... View more
11-28-2023
05:41 AM
|
0
|
0
|
1176
|
|
POST
|
Here is another data point in terms of hardware for up-to 25 users: https://www.esri.com/content/dam/esrisites/en-us/media/pdf/hardware-partners/dell/dellvirtualizationappliance.pdf Not apples-to-apples, but gives some context.
... View more
11-20-2023
04:31 AM
|
1
|
0
|
2893
|
|
POST
|
We support PostgreSQL also and have had many clients move that direction.
... View more
11-17-2023
12:51 PM
|
0
|
1
|
17535
|
|
POST
|
Ok, my hunch may have been correct....... you need to update the version of SQL Server to at least SQL 2016 to be on a supported version of SQL Server (https://enterprise.arcgis.com/en/system-requirements/latest/windows/database-requirements-sqlserver.htm). I would recommend something newer like 2019 or 2022 for the SQL version to get more mileage. I do not think that version of SQL Server has been supported since before Enterprise 10.9.1 / Pro 2.9 in terms of our clients and DBMS combinations. I would look at upgrading the geodatabase to a newer version: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/upgrade-geodatabase-sqlserver.htm I would also make sure that you verify any dependencies on the geodatabases to other GIS systems, like Enterprise.
... View more
11-17-2023
12:31 PM
|
1
|
7
|
17542
|
|
POST
|
Getting the version of the geodatabase and RDBMS would be most helpful for any potential troubleshooting. Have your admin query the SDE_version table and return the info for the geodatabase side.
... View more
11-17-2023
11:54 AM
|
0
|
9
|
17550
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | a week ago | |
| 1 | 2 weeks ago | |
| 2 | 3 weeks ago | |
| 1 | 3 weeks ago | |
| 2 | 07-01-2026 04:09 AM |
| Online Status |
Offline
|
| Date Last Visited |
Thursday
|