POST
|
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?
... View more
a week ago
|
0
|
0
|
88
|
POST
|
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
... View more
a week ago
|
0
|
0
|
100
|
BLOG
|
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! 🎉
... View more
|
5
|
0
|
106
|
POST
|
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.
... View more
2 weeks ago
|
0
|
1
|
178
|
POST
|
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
... View more
2 weeks ago
|
0
|
0
|
83
|
POST
|
Yeah, that is a not what I would expect. I would contact technical support and work with them on this. This is the best path forward. It seems that the roll back was not 100% successful (given I am not sure how you did this).
... View more
2 weeks ago
|
0
|
0
|
366
|
POST
|
If you run the PatchFinder tool, what does it report? It should at least report the version of Esri software installed. What is the OS that you have 10.9.1 deployed on?
... View more
2 weeks ago
|
0
|
4
|
380
|
POST
|
You may also want to look at the append tool: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/append.htm I know that they are making improvements with each release.
... View more
3 weeks ago
|
1
|
0
|
239
|
POST
|
For the data in SQL EGDB that is branch versioned, you cannot use truncate against versioned data: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/truncatetable.htm If you need to truncate, you must UNVERSION the data first in Pro. That is why the delete rows works against the service.
... View more
3 weeks ago
|
1
|
0
|
242
|
POST
|
Is the data in the SQL database already branch versioned and published to Enterprise for the parcel fabric?
... View more
3 weeks ago
|
1
|
0
|
317
|
POST
|
I would recommend contacting Technical Support on this. It may take more detailed troubleshooting than we can accomplish in this forum. If you enable the database as a geodatabase and register that layer with the geodatabase, I wonder if the behavior is different.
... View more
3 weeks ago
|
0
|
0
|
182
|
POST
|
Once you restore the DB you have to re-sync the logins for the DB users, no OS users: https://support.esri.com/en-us/knowledge-base/re-synch-sql-server-logins-or-users-after-restoring-a-d-000008079 That should allow the data owners & SDE to connect without any issues. The reason the IT manager can access is probably due to their user being a SYSADMIN on the SQL instance. I would possible have the IT admin undo what they did to get the DB users access to SDE.
... View more
3 weeks ago
|
1
|
2
|
68
|
POST
|
We do NOT recommend loading data as the SDE user and would create a separate DB user / schema to own the data: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/add-users-postgresql.htm That error message "database user name and current user schema do not match" is expected, see the doc link above. You them grant other users permissions to view and / or edit: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-postgresql/privileges-postgresql.htm Hope this helps!
... View more
3 weeks ago
|
2
|
0
|
129
|
POST
|
I am not sure on that specific error message. Do you have a need to the Z value to be enabled? If not, may want to recreate it without the Z value.
... View more
3 weeks ago
|
1
|
2
|
203
|
Title | Kudos | Posted |
---|---|---|
5 | a week ago | |
1 | 3 weeks ago | |
1 | 3 weeks ago | |
1 | 3 weeks ago | |
1 | 3 weeks ago |
Online Status |
Online
|
Date Last Visited |
an hour ago
|