Latest Contributions by ShannonShields

‎09-24-2024

Stephen, changing the .sde file in a project is not going to change the connection information stored in each individual layer. If you are using the UpdateConnectionProperties to swap out the .sde file, that is only changing the .sde file in the project. You'd have to update the individual layers one at a time. However, when using Entra MFA the user is still going to need to supply their credentials at least once. If all the layers are from the same database, the first prompt to supply credentials should then apply to all the remaining layers. Have you tried testing simply creating a project with a few layers pulled from a single connection made with MFA and with 'save user/password' unchecked and having another user open the project? In my testing (using ArcGIS Pro 3.3) I am only prompted for my MFA credentials once when opening a project containing layers that I have permission to see but that were added by another MFA login. -Shannon

‎09-24-2024

Annette, when tables or feature classes are part of a SQL Server geodatabase and created via ArcGIS then the ObjectID values are managed/generated by two stored procedures and a table that allow for IDs to be generated in larger blocks, and also manage multiple simultaneous users adding features. There is a stored procedure sde.next_rowid() (or dbo.next_rowid) that takes a geodatabase table/feature class as input and returns the next value for the ObjectID field. It uses the related stored procedures and ID table so IDs do not get reused and the sequence of subsequent IDs is preserved. That might be an option for the ETL operation. But, do these tables need to be registered with the geodatabase? You can still interact with them in a read-only capacity without them having to be registered. Then you are free to manage a unique identifier field however you want - you can make the ObjectID an Identity field and have it auto-increment that way. -Shannon

‎04-16-2024

Using the JOIN syntax makes things a little easier to understand - you can see what each join is based on, and you can also specify that all records in a table are returned even with no matches (those NULL records you indicated were problematic) by using an outer join - LEFT JOIN or RIGHT JOIN syntax. -Shannon

‎04-15-2024

Glad you got it all worked out!

‎04-08-2024

1 - They wondered if it was possible to have two authentication types running at the same time. For instance, when the user first initially creates a New Database Connection...they could use Windows Authentication for that component. When the user seeks to add or begin to edit a feature class...they would need to use Database Authentication to proceed. I'm not sure if I understand what they are wanting here. When you make a database connection, you can only connect as a single login. The connection is made as an Operation System/Active Directory login, or it is made as a database-managed login. You cannot do both at the same time. You could make a second connection as a different login, but that would be a second connection, and it would be a weird workflow to switch back and forth between different connections during the same session. I think you need to figure out your workflow - are people creating a lot of new feature classes all the time? Or is there a pretty fixed schema and most people are simply viewing or editing existing data? Once you determine this, then you can figure out who needs the ability to create objects, and who only needs to work with existing data. 2 - When you copy the datasets using the 'Holly' connection, you are getting a new copy of the tables, all owned by Holly, so she has view & edit permission automatically as she created the datasets. 'Dale' cannot see anything because he has not been granted permission to see the data. This is a separate step after the data has been created. Also, given that you have put Dale in the Viewer role, you don't need to explicitly grant to Dale - you can grant to the Role. But the role has to be granted privileges too. That is the missing step here - by default a new feature class or table is invisible to anyone other than the person who created it. They would need to grant permission to view or edit that table to users or roles. -Shannon

‎04-05-2024

I've gone through your post a couple of times and need to clarify a couple of things: 1 - When you say I would also like to have them use database authentication when they are going to edit. are you meaning you want them to be able to create new feature classes/tables, or do you want them to edit existing feature classes & tables? 2 - That first statement seems to sort of contradict this one I would like the database connection to be added using their Windows Authentication. Or are these users not going to create feature classes & tables, but only work with existing ones? I'd break my users down into 3 categories: Data Creators - these users have elevated privileges that allow them to create feature classes, views & tables in the database. They are the "owner" of those objects and certain operations from ArcGIS must be done as the owner (like granting permission to other users). Data Editors - these users do not create tables, but they have permission to edit data in existing tables & feature classes Data Readers - these users have no permission beyond the ability to read existing tables/feature classes Are you wanting Data Creators to use a single, database login when they create data so that it all goes on a common schema? But users who will work with that data (editing & reading) will connect using their windows logins? -Shannon

‎04-05-2024

Hi Josh, traditional versioned feature classes & tables have additional side tables to manage the edits. Based on the screenshot you provided it looks like permissions have not been granted to those tables - A# and D#. Each versioned table will get one set, and the names are based on the registration Id of the business table. Using the ArcGIS tools to grant permission is going to ensure that any related object has permission granted as well. The downside to those tools is that permissions need to be granted by the user that created the tables. You can absolutely continue to have your DBA manage permissions, but they need to understand all the related objects that also need to have permissions applied. -Shannon

‎05-25-2023

ST_Geometry libraries are available for download on My Esri with each version of Pro that is available. At 11.1 they are also available for separate download for ArcGIS Enterprise. For Oracle, ST_Geometry libraries are built for specific ArcGIS releases. For PostgreSQL they are built for each supported PostgreSQL release supported with that ArcGIS release. If the version of Oracle or PostgreSQL is no supported with the ArcGIS release, an older ST_Geometry library is not going to change this. For more information on supported Oracle releases see: https://enterprise.arcgis.com/en/system-requirements/latest/linux/database-requirements-oracle.htm For information on configuring the ST_Geometry libraries for use in an Oracle geodatabase see: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-oracle/configure-oracle-extproc.htm

‎05-24-2023

Support for SQL Server Auto Grid spatial indexes was provided in 10.3.1 for SQL Server database compatibility level 110 and higher.

‎05-24-2023

The SDEBINARY data type has been deprecated. Please see https://support.esri.com/en-us/knowledge-base/deprecation-enterprise-geodatabase-support-of-binary-sp-000030270 for more information. Database views created against native spatial types have been supported in ArcGIS for many releases.

‎05-24-2023

Editor Tracking and Attribute Rules provide this functionality.

‎05-24-2023

The Create Database View geoprocessing tool lets you create a view in a geodatabase, and the Register with Geodatabase geoprocessing tool supports the registration of views with the geodatabase.

‎05-23-2023

ArcGIS Desktop 10.2.1 was retired in 2019 and this idea no longer applies to currently released software.

‎05-01-2023

Yes, testing has been completed. The online documentation for 3.1/11.1 & 3.0/11.0 has been updated. The updates for 2.9/10.9.1 online documentation should be published by early June. However, 2022 is supported even if the doc doesn't fully reflect it yet. https://enterprise.arcgis.com/en/system-requirements/latest/windows/database-requirements-sqlserver.htm (there is an 'Other versions' drop down to see earlier releases.

‎03-17-2023

6 million features is not especially large, but 800 separate feature classes is. Do you have a lot of relationship classes? Domains? More complex datasets like topologies? Given the 800 separate feature classes I'd be reluctant to recommend importing empty schema and then appending data - that is a lot of separate append operations to coordinate. If you have a lot of 'behavior' like domains & relationship classes then they will get preserved and imported along with the data if you copy and paste directly from one workspace into the other. Using a tool like Export will not preserve any of the behavior, and will only bring across data. Have you tested any of these methods yet to determine if your data is actually too large?

Online Status	Offline
Date Last Visited	a month ago

My Ideas

Latest Contributions by ShannonShields

Re: Using arcpy.mapping to change user for SDE connections using Microsoft Entra MFA authentication

Re: OBJECTID - configuring auto increment via SQL Server post feature class creation

Re: Edit Query Layer SQL Select Statement Question

Re: Adding Logins, Users, & Privileges using SSMS & ArcGIS Pro

Re: Adding Logins, Users, & Privileges using SSMS & ArcGIS Pro

Re: Adding Logins, Users, & Privileges using SSMS & ArcGIS Pro

Re: Best Practices with Granting Privileges and Versioning Data

Re: Provide older versions of ST_GEOMETRY .dll in My Esri downloads - Status changed to: Already Offered

Re: DEFAULT GEOMETRY_AUTO_GRID for SQL Server 2012 Spatial Index - Status changed to: Implemented

Re: Need ability to create spatial view in an Enterprise Geodatabase if the storage geometry is SDEBINARY - Status changed to: Closed

Re: Support SQL Triggers in ArcSDE - Status changed to: Already Offered

Re: Ability to create a spatial view inside of ArcMap in the Geodatabase Admin Toolbox - Status changed to: Implemented

Re: SQL Server 2016 support for ArcGIS Desktop version 10.2.1 - Status changed to: Closed

Re: Will ArcGIS Enterprise support SQL Server 2022 Standard

Re: Migrate from FGDB to SDE

Re: OBJECTID - configuring auto increment via SQL ...

Re: Adding Logins, Users, & Privileges using SSMS ...

Re: Adding Logins, Users, & Privileges using SSMS ...

Re: Best Practices with Granting Privileges and Ve...

Re: Will ArcGIS Enterprise support SQL Server 2022...