Latest Contributions by ShannonShields

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 ... View more

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. ... View more

If you are working with curve geometry features, I wouldn't recommend using ST_Area & ST_Length functions, which are used to display those values dynamically when you view attributes. Features with curve geometry/circular arcs have two representations in enterprise geodatabases. The ST_Geometry shape stores a densified arc version of the geometry, and the true curve is stored in a blob format read by ArcGIS, but not by the DBMS. If you use the Measure tool in Pro you'll see the measurement based on the curve geometry. You can calculate your own area/length fields using the Calculate Geometry Attribute tool, and there are Arcade Geometry functions for area & length if you want to have these values automatically generated using Attribute Rules. This applies to all spatial types in enterprise geodatabases including Oracle Spatial, SQL Server Geometry/Geography, PostGIS as well as ST_Geometry on Oracle & PostgreSQL. We understand that this is confusing and not a great user experience. We are investigating ways to improve this behavior so that it is easier to get to the consistent measurement value. ... View more