POST
|
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
... View more
a week ago
|
0
|
2
|
108
|
POST
|
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
3 weeks ago
|
1
|
2
|
207
|
POST
|
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
... View more
3 weeks ago
|
1
|
5
|
259
|
POST
|
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
... View more
3 weeks ago
|
1
|
0
|
227
|
IDEA
|
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
... View more
05-25-2023
11:42 AM
|
0
|
0
|
298
|
IDEA
|
Support for SQL Server Auto Grid spatial indexes was provided in 10.3.1 for SQL Server database compatibility level 110 and higher.
... View more
05-24-2023
03:32 PM
|
0
|
0
|
400
|
IDEA
|
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.
... View more
05-24-2023
03:28 PM
|
0
|
0
|
130
|
IDEA
|
Editor Tracking and Attribute Rules provide this functionality.
... View more
05-24-2023
03:25 PM
|
0
|
0
|
194
|
IDEA
|
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.
... View more
05-24-2023
09:50 AM
|
0
|
0
|
569
|
IDEA
|
ArcGIS Desktop 10.2.1 was retired in 2019 and this idea no longer applies to currently released software.
... View more
05-23-2023
04:35 PM
|
0
|
0
|
284
|
POST
|
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
05-01-2023
11:02 AM
|
4
|
0
|
2053
|
IDEA
|
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?
... View more
03-17-2023
02:31 PM
|
0
|
0
|
902
|
POST
|
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
03-17-2023
11:42 AM
|
1
|
2
|
771
|
POST
|
what was the error? Are you using double-quotes around the schema & user name, and if so try dropping them.
... View more
01-24-2023
11:54 AM
|
0
|
1
|
831
|
Title | Kudos | Posted |
---|---|---|
1 | 3 weeks ago | |
1 | 3 weeks ago | |
1 | 3 weeks ago | |
4 | 05-01-2023 11:02 AM | |
1 | 03-17-2023 11:42 AM |
Online Status |
Offline
|
Date Last Visited |
Tuesday
|