Latest Contributions by George_Thompson

Ah, ok. Remove the SYSADMIN and the other permissions that you checked "on" in the DB from the GIS user. That should hopefully get you back to the place you need to be. You should never have to assign a user SYSADMIN for geodatabase functions, unless DBO schema and not the DB owner. Regardless if you create a new user and grant them SYSADMIN it will not work as expected. Hope this helps!

Ok...... so the data is "owned" by the "GIS" user. Using SYSADMIN will not allow you to take over the data, like an owner. You will need to login to the EGDB as the GIS user in order to fix this issue. I would back out all the permissions that you set based on the document provided to you. It is possible that the workflow worked in the past, but not now.

Questions: Did you select all the permissions in the screenshot manually? I would uncheck the db_owner permission on that DB. Since you are SYSADMIN, you should have the correct permissions as you "mimic" the DBO user. Just verifying that you have a DBO schema enterprise geodatabase? i.e., all data is owned by DBO user. A guess is that your UN / schema do not match and the mixed permissions are causing an issue.

I just saw the technical article about the update service and posted it.

Here is an explanation as to why: https://support.esri.com/en-us/knowledge-base/calculate-field-does-not-honor-selection-or-layer-filt... Related to an issue found with Pro 3.5 and using SQL in Field Calculator: "This issue will be addressed in 3.5 Patch 1 (3.5.1), planned to be available the first week of June 2025. Until a patch is available, the software update service will be disabled in ArcGIS Pro. Customers who understand this issue and the workaround can download ArcGIS Pro 3.5 from My Esri."

Here is an explanation as to why: https://support.esri.com/en-us/knowledge-base/calculate-field-does-not-honor-selection-or-layer-filte-000036268 Related to an issue found with Pro 3.5 and using SQL in Field Calculator: "This issue will be addressed in 3.5 Patch 1 (3.5.1), planned to be available the first week of June 2025. Until a patch is available, the software update service will be disabled in ArcGIS Pro. Customers who understand this issue and the workaround can download ArcGIS Pro 3.5 from My Esri."

Here a blog that was just released related to this: https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/enhancing-accuracy-together-the-new-and-improved-esri-basemap-feedback-service

If the feature class is being used in a service, I would stop that service and try to delete. Is the data versioned? If not, you could try to copy out all the good records, then truncate the table (should drop all records). Make sure you have a backup of the data before truncate. This would be the last option I would use.

You can copy in a layer from a file geodatabase that has some spatial information. It will create it in SQL Server which you can then bring into Pro and publish.

I have not tested with just a table; I usually have a spatial layer. You could try to create a spatial layer in the same database with 1 record, turn it off when publishing. Here is some more information on publishing from a database: https://enterprise.arcgis.com/en/server/latest/publish-services/linux/prepare-data-for-feature-services.htm#ESRI_SECTION1_C30D73392D964D51A8B606128A8A6E8F What version of Enterprise are you publishing the table to?

If you are connecting to the PostgreSQL instance in Azure from your local machine you may experience some latency with the data. We highly recommend that you have the Pro client in the same VNet as the PostgreSQL instance for best performance. Is the PostgreSQL an enterprise geodatabase or just a PostgreSQL database? From the video it looks like you are experiencing the issue when connecting to a service that is published to Enterprise, correct? Can you also provide the versions of Enterprise / Pro installed? Are they fully patched?

I would recommend using AD groups. Add them to the SQL instance, map them to GDB A & B (connect only), then in Pro assign the editing permissions to the groups (this must be done as the feature class owner). That should allow them to just edit data in the allowed feature classes (or related objects). Here is some doc to help with the process: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/user-accounts-groups.htm#ESRI_SECTION1_97D393C792C641F8B21706C3ECDCDED6 https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/add-users-sqlserver.htm#ESRI_SECTION1_1EF70F32F80041FB9666781BD3D78754 https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-sql-server/privileges-sqlserver.htm

I love to see that number growing year after year. Congratulations to all the people who have earned a certification so far, and to the ones in the future! 🎉

‎04-28-2025

How are you adding the new account: Pro tool / via SSMS? Can you also expand on what "with sde schema to a geodatabase" means? From the error message, it seems that permissions on the sde schema are not public or were changed.

‎04-25-2025

Are you connected as the data owner for that feature class? It looks like the data is owned by DBO. That user would need to enable that functionality. https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/register-as-versioned.htm

Online Status	Offline
Date Last Visited	16 hours ago

My Ideas

Latest Contributions by George_Thompson

Re: I am the data owner, but am getting User is not the data owner message

Re: I am the data owner, but am getting User is not the data owner message

Re: I am the data owner, but am getting User is not the data owner message

Re: Pro Update (Update to 3.5) Service Down

Re: ESRI update service is temporarily unavailable

Re: Pro Update (Update to 3.5) Service Down

Re: Updating Basemaps (for Pro?)

Re: Cannot delete feature with Null Shape_Area (SDE)

Re: Is there a way to edit a SQL DB Table (as a standalone table) in ArcGIS Pro?

Re: Is there a way to edit a SQL DB Table (as a standalone table) in ArcGIS Pro?

Re: How slow is too slow when using ArcGIS Enterprise with a PostgreSQL backend?

Re: failed to connect to the specified DBMS instance(sqlserver)

Re: Celebrating 15K Certifications Earned!

Re: failed to connect to the specified DBMS instance(sqlserver)

Re: Manage Geodatabase Functionality Not Saving

Re: Pro Update (Update to 3.5) Service Down

Re: ESRI update service is temporarily unavailable

Re: Pro Update (Update to 3.5) Service Down

Re: Updating Basemaps (for Pro?)

Re: Cannot delete feature with Null Shape_Area (SD...

Cloud Computing

Esri Certified Individuals