Latest Contributions by BillFox

take a look at the similar setup for spatio-temporal data stores ... View more

your move to ha will involve a lot more than that step if you have the option, build it from scratch ... View more

Does ArcGIS Enterprise still impose a limit of 16 characters for attribute index names? https://community.esri.com/t5/arcgis-enterprise-questions/does-arcgis-enterprise-still-impose-a-limit-of-16/m-p/1626250#M42483   ... View more

https://docs.oracle.com/en/database/oracle/oracle-database/23/odpnt/EFCoreIdentifier.html Identifier Name Length and Uniqueness   Oracle Database limit identifier names, such as table names, column names, and primary key names, to 128 bytes. Oracle Entity Framework Core will automatically truncate identifier names that are too long to this specified length, except for table names. This prevents both the user and Entity Framework Core from creating identifiers beyond the maximum character limit of the Oracle Database and receiving an "ORA-00972: IDENTIFIER IS TOO LONG" error” in most instances. If the identifiers use multi-byte characters, the maximum identifier length may require a setting with character expansion ratio in mind to assure that all identifiers can be created in the Oracle database. For example, if the Oracle database character set is UTF8, a single character may require up to 4 bytes. Thus, to guarantee that all identifiers can be created in an Oracle database that does not support long identifiers, the RelationalAnnotationNames MaxIdentifierLength field can be set to 32 bytes (i.e. 128 bytes divided by 4). By default, Oracle EF Core MaxIdentifierLength has a value of 128. Even if your EF Core model does not use identifier names longer than what your database version supports, you should consider setting MaxIdentifierLength to a lower value. ODP.NET and Entity Framework Core auto-generate schema object names from models. They may, on occasion, append additional characters to the names, which could exceed the maximum number of characters the database permits. By setting the MaxIdentifierLength, you prevent EF Core from causing the ORA-00972 error inadvertently. ... View more

Index name 16 if created in ArcGIS. ArcGIS can read up to the database limit for indexes created outside ArcGIS.   ArcGIS imposes a limit of 16 characters for index names created within ArcGIS in most databases. However, for SQL Server and SQLite, index names can be up to 128 characters. If the index is created outside ArcGIS, ArcGIS can read up to the database's maximum limit for index names. Additionally: Index names must start with a letter and cannot contain spaces or reserved database keywords. ArcGIS does not support object names requiring delimiters (e.g., double quotation marks). If you need further details about specific databases or scenarios, feel free to ask! ... View more

Index name 16 if created in ArcGIS. ArcGIS can read up to the database limit for indexes created outside ArcGIS. https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage-oracle/enterprise-geodatabase-limits.htm   ... View more

what is oracle spatial   Oracle Spatial is an optional feature of the Oracle Database Enterprise Edition that provides advanced geospatial capabilities. It is designed to store and manage spatial data, such as geographic features represented by points, lines, and polygons. Oracle Spatial supports the SDO_Geometry type, which is implemented using Oracle's extensible object-relational type system. Key features of Oracle Spatial include: Geodetic Data Support: It supports geodetic coordinates (latitude and longitude) for measuring the Earth's surface. SQL Access: Provides ISO and OGC-compliant SQL access to spatial data. Efficient Storage: Designed to efficiently use database resources and support features like replication and partitioning. Compatibility: Works with ArcGIS to manage feature and raster datasets in enterprise geodatabases or Oracle databases. Oracle Locator is a subset of Oracle Spatial capabilities and is included as a standard feature in Oracle Database Standard and Enterprise editions. ... View more

which databases require that limit?   The 16-character limit for attribute index names in ArcGIS is imposed to ensure compatibility across all supported databases and facilitate data sharing between geodatabases. Specifically: Oracle Spatial has a stricter limitation, allowing up to 18 characters for spatial index names, with two characters reserved for appending "_A." SQL Server and SQLite allow longer index names (up to 128 characters), but ArcGIS enforces the 16-character limit to maintain consistency across geodatabases. This restriction is based on the smallest allowable length within supported databases. ... View more

Esri Support AI Chatbot     Hello! I'm the Esri Support AI Chatbot, a digital assistant designed to help you troubleshoot ArcGIS issues and answer any technical questions you might have. For more details about what I can do, please select the question mark icon at the top of our chat. How can I help you today? Does ArcGIS Enterprise still impose a limit of 16 characters for attribute index names?   Yes, ArcGIS Enterprise continues to impose a limit of 16 characters for attribute index names. This restriction is designed to ensure compatibility across supported databases and facilitate seamless data sharing between different geodatabases.   ... View more

bundle? https://community.esri.com/t5/arcgis-enterprise-ideas/enterprise-automated-tls-certificate-renewal/idi-p/1606325   ... View more

@KimPeter  ... View more

so far, it reads we are locked into branch for things like utility network and parcel fabric is esri going to allow traditional versioning for those too? ... View more

so another complete re-read of the versioning  documentation... "Because an enterprise geodatabase can contain datasets with a mixture of versioning types, it is important to understand the implementation and usage workflows supported for each type." https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/overview-of-versioning-in-arcgis-pro.htm   ... View more

have you tried it without python, "Interactively" , step-by-step? ... View more

🤔 and the list goes on, only a single level of versions, No "posting version" between protected default and private editor version, etc. what a shake-up Considerations Consider the following when editing the data in a named version: Branch versioning allows only one level of named versions to be created from the default version. In other words, you cannot create a named version from a named version. Only one editor per named branch version is allowed, or multiple users can read from the named version. Once an editor begins editing data in a named version, an exclusive lock is obtained and no other user can connect to the version. You can undo and redo edits when editing the data in a named version. Reconcile and post operations are done using the default version as the target version; you cannot reconcile with or post to another named version. Because the branch versioning model is a temporal model in which all records and edits are tracked in the same base table, there is no requirement to compress. ... View more