Description
In ArcGIS Pro 3.0, there is a temporary limitation where large tables with 2.5 million or more rows consume a significant amount of machine memory, leading to performance problems and stability issues. For these large tables, the first 100,000 rows are loaded, but if the user scrolls down until 2.5 million rows are loaded, clicks 'Load All' or 'Go to Last Row' on the table, a warning related to the table size and suggesting the use of definition queries for the dataset is returned, as shown in the image below. The table then closes.
Cause
This issue is caused by a .NET 6.0 component upgrade.
Solution or Workaround
Warning:
The instructions below include making changes to essential parts of your operating system. It is recommended that you backup your
operating system and files, including the registry, before proceeding. Consult a qualified computer systems professional, if necessary.
Esri cannot guarantee results from incorrect modifications while following these instructions. Therefore, use caution and proceed
at your own risk.
Several things can be done to continue working with these larger datasets:
- Work with selections and selected-row mode in the table as much as possible.
- Do not use the ‘Load All’ or ‘Go to last row’ commands, especially for ancillary tasks such as seeing the full row count. To get large row counts, use the Get Count geoprocessing tool.
- Use definition queries to filter the data. Layers can now store many definition queries, so users can create multiple queries for a large datasets and switch between them.
- Note that workflow tasks, such as creating selection sets through Select by Attributes and using Find (Ctrl-F), are still supported against the full dataset. It is only the loading of the rows into the active table view that is impacted.
- If workflows require the full loading of large datasets into the table view, Esri recommends that users continue to work with ArcGIS Pro 2.9.x or earlier until we can address this issue in a patch for 3.0.
- If for some reason you require the full loading of large datasets in the table view and must work in ArcGIS Pro 3.0, a registry key can be used to allow larger tables to remain open. The value is hexadecimal and represents the maximum number of rows that can be opened in a table. To apply this, create a Double Word TableMaxRows registry entry under the HKEY_CURRENT_USER\Software\ESRI\ArcGISPro\Settings folder using the Windows Registry Editor, as shown in the images below. This option must be considered with extreme caution, as it may cause performance and stability issues for table views in ArcGIS Pro 3.0.
- Key Location – Computer\HKEY_CURRENT_USER\SOFTWARE\ESRI\ArcGISPro\Settings
- Key Name – TableMaxRows (DWORD)
- Key Value – the number of rows to allow before closing the table. If the key is missing or deleted, a default value of 2.5 million will be used