Latest Contributions by MarceloMarques

@wilcow - Let me try to explain. Geodatabase Traditional Versioning: You have child versions of sde.default that you reconcile and post to sde.default, then via ArcGIS Pro you can see that the edits are now present in the sde.default, but if you look the featureclass or table directly in the database you might not see that the edits are there, then you decide to run a sde compress, this shall then move the rows from the delta tables ( Adds Table and Deletes Table ) to the base table (traditional versioning), in a normal situation this is what will happen, but there are many factors that can make the data to remain in the delta tables, for example, it might have child version of sde.default that are pinning the state lineage version tree, hence the sde compress cannot move the rows, the sde compress will still trim the state lineage tree, but only after those child versions are reconciled, posted and deleted that the sde compress will be able to move the rows from the delta tables to the base tables. This situation and others are well explained in the training classes below. Implementing Versioned Workflows in a Multiuser Geodatabase | Esri Training Instructor-Led Course Deploying and Maintaining a Multiuser Geodatabase | Esri Training Instructor-Led Course You might never be able to achieve state 0 with sde compress if you need to keep child versions of sde.default, the only way is to reconcile, post and delete all child versions and then run sde compress multiple times. And after that you need to gather new statistics and rebuild indexes (attribute indexes and spatial indexes) and gather new statistics again. Geodatabase SQL Access: Now, if you have an external application that needs to access the data, then that application can use the multi-versioned views to query the geodatabase data in the sde.default version. For more information see the documentation below. SQL access to enterprise geodatabase data—ArcMap | Documentation (arcgis.com) ArcGIS Compatibility: About ArcGIS Server 10.6.1 & ArcGIS Pro & Geodatabase ArcSDE Repository Compatibility. Client and geodatabase compatibility—ArcGIS Pro | Documentation Client and geodatabase compatibility—ArcGIS Server | Documentation for ArcGIS Enterprise You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so. Geodatabases and client software are designed to work together, and if you let one get too many releases away from the other, you risk encountering problems or unexpected behavior. This is especially true when you use a mix of client versions at your site. A newer client can create newer dataset types in the geodatabase that older clients cannot access. For enterprise geodatabases, waiting too long between geodatabase upgrades may mean you have to upgrade the underlying database more than once before you can upgrade the geodatabase. ArcMap 10.6.1 & ArcGIS Server 10.6.1 are retired as January 1, 2024. | Version | Release date | General Availability | Extended | Mature | Retired | ArcMap Life Cycle | Esri Support 10.6.1 July 17, 2018 Jul 2018–Dec 2019 Jan 2020–Dec 2021 Jan2022–Dec 2023 January 1, 2024 ArcGIS Enterprise Life Cycle | Esri Support 10.6.1 July 17, 2018 Jul 2018–Dec 2019 Jan 2020–Dec 2021 Jan 2022–Dec 2023 January 1, 2024   IMPORTANT NOTE: ArcGIS 10.8.2 is the current release of ArcMap and will continue to be supported until March 01, 2026. We do not have plans to release an ArcMap 10.9.x. This means the 10.8.x series will be the final release series of ArcMap and will be supported until March 01, 2026. REMARKS: If you want to use ArcGIS Server with ArcGIS Pro then the advice is to move the deployment to a more recent release, it might be difficult to upgrade your current environment, and it might be easier to create new servers, deploy and configure the new ArcGIS software and republish the ArcGIS Server Services. ArcGIS Pro 3.2.2 ArcGIS Server 11.2 SQL Server 2022 + Latest Cumulative Security Update ArcSDE Geodatabase Repository 11.2.0.3.2 FAQ: What SQL Server Database Versions Are Supported by ArcGIS Enterprise and ArcGIS Pro? (esri.com) ArcGIS 11.2 and ArcGIS Pro 3.2 requirements for Microsoft SQL Server—ArcGIS Enterprise | Documentation for ArcGIS Enterprise ArcGIS Pro Life Cycle | Esri Support I hope this helps. ... View more

@PatOBrien - Esri rarely makes announcements about the date of the next release, but if you look the release dates in the Life Cycle documentation it will give you an idea of when the next release might be available. ArcGIS Enterprise Life Cycle | Esri Support ArcGIS Pro Life Cycle | Esri Support ... View more

@TimLangner  - As long as you are running a supported SQL Server version for ArcGIS Pro 3.2 then you shall be able to connect to an older version of the ArcSDE Geodatabase like 10.6.1. FAQ: What SQL Server Database Versions Are Supported by ArcGIS Enterprise and ArcGIS Pro? (esri.com) ArcGIS 11.2 and ArcGIS Pro 3.2 requirements for Microsoft SQL Server—ArcGIS Enterprise | Documentation for ArcGIS Enterprise Microsoft SQL Server database requirements for ArcGIS 10.8.x and ArcGIS Pro 2.5, 2.6, and 2.7—System Requirements | Documentation Important Note: Client and geodatabase compatibility—ArcGIS Pro | Documentation "You do not have to keep your geodatabase and ArcGIS clients at the same release, but it is recommended that you do so. Geodatabases and client software are designed to work together, and if you let one get too many releases away from the other, you risk encountering problems or unexpected behavior." "This is especially true when you use a mix of client versions at your site. A newer client can create newer dataset types in the geodatabase that older clients cannot access. For enterprise geodatabases, waiting too long between geodatabase upgrades may mean you have to upgrade the underlying database more than once before you can upgrade the geodatabase." For more best practices. Mapping and Charting Solutions (MCS) Enterprise Da... - Esri Community How Load Large Featureclass SQL Server Geodatabase How to Move the SQL Server Enterprise Geodatabase with a database backup How to Install Database Clients for ArcGIS How to Install the SQL Server Client for ArcGIS? I hope this helps. ... View more

@ScottFortman1 - I am adding this comment so others can understand. ArcCatalog 10.8.2 cannot delete the *Subtype field. But if we go to the "Subtypes" tab and set to <None> then under the "Fields" tab will be able to delete the Subtype field. Workaround ... View more

yes, you cannot delete the *Subtype field if the Featureclass was created with one from the beginning, this because the *Subtype field is how the data gets organized, hence the only way around this is to create a new Featureclass without the *Subtype field and reload the data. ... View more

@ScottFortman1 - ArcGIS Pro will not let you delete the *Subtype field, that is expected behavior. You will need to create a new empty Featureclass with the new fields and domains that you want then you will reload the data using the old Featureclass. ... View more

@ScottFortman1 - If you are using an ArcSDE Enterprise Geodatabase then you can be locking yourself, try to close ArcGIS Pro / ArcCatalog, then connect again with the data owner user, do not click any other geodatabase connection file, and try again to make the schema change, you also need to ask all other users to disconnect and stop all ArcGIS Server Services that use the ArcSDE Enterprise Geodatabase that you are trying to make schema changes. ... View more

@Yogesh_Chavan - you are welcome, glad to assist.  : ) ... View more

@tbearb - glad to assist.  : ) ... View more

@Yogesh_Chavan  Question: Is it possible to change the name of the Portal & Server Webadaptors ??? Answer: From the technical support this is unsupported, here's the doc that refer to: https://enterprise.arcgis.com/en/portal/latest/administer/windows/using-a-reverse-proxy-server-with-portal-for-arcgis.htm Integrate your portal with a reverse proxy or load balancer—Portal for ArcGIS | Documentation for ArcGIS Enterprise Question: Does Esri supports to rename the webapators ??? Answer: No, it is not a supported workflow. Question: Can Esri Technical Support assist to rename the webadaptors??? Answer: No, it cannot, it is not a supported workflow. Question: Can Esri Professional Services assist to rename the webadaptors ??? Answer: Yes, Esri Professional Services has tools and methods that can be used to rename the webadaptors, the customer can reach out to Esri Professional Services for assistance. I hope this clarifies your question. ... View more