Statistics are updated for tables and indexes on this dataset as described at the beginning of this topic. You can use the Analyze Datasets geoprocessing tool located in the Geodatabase Administration toolset of the Data Management toolbox to update statistics. Use this tool instead of the Analyze command in ArcMap if you want to update statistics on several datasets at once, if you want to choose the specific tables that are analyzed for example, if you only want to update statistics on the delta tables , or if you want to update statistics on the geodatabase system tables.
You must run the tool as the owner of the tables you want to analyze. In the case of geodatabase system tables, you must run the tool as the geodatabase administrator. You should update statistics on the geodatabase system tables after many new tables or feature classes have been added to the geodatabase, a large number of versioned edits have been performed, or the geodatabase has been compressed.
Connect as the owner of the tables to be analyzed. You can type the tool name into the Search field to find the tool and open it, or browse to the tool in the Geodatabase Administration toolset of the Data Management toolbox. Statistics are updated for the tables you chose and their indexes. When you run the following Python script, specify a database connection file. The script updates statistics for all tables owned by the user specified in the connection.
For example, to run this script on Linux using the database connection file entgdb. To run this script to update statistics on system tables, specify a connection file that connects as the geodatabase administrator. Arc GIS Desktop. Available with Standard or Advanced license. Name: AnalyzeDatasets. The timestamp when this statistics row was inserted or last updated. The total number of rows or LOBs in the table space or partition.
Indicates the number of rows in all tables for multi-table table spaces. The number of active pages in the table space or partition. Indicates the total number of preformatted pages in all data sets for multi-piece table spaces. The amount of space in kilobytes that is allocated to the table space or partition. Indicates the amount of space in all data sets for multi-piece linear page sets. The number of extents used by the table space or partition. Indicates the number of extents for the last data set for multi-piece table spaces.
For a data set that is striped across multiple volumes, the value is the number of logical extents. Does not include LOB updates because they are implemented as deletions followed by insertions. A LOB is perfectly chunked if the allocated pages are in the minimum number of chunks.
A record is well-clustered if the record is inserted into a page that is within 16 pages of the ideal candidate page. For non-segmented table spaces, a page is near the present page if the two page numbers differ by 16 or less. For non-segmented table spaces, a page is far the present page if the two page numbers differ by more than The timestamp of the last full or incremental image copy on the table space or partition.
The number of distinct pages that have been updated since the last COPY was run. The data set number within the index space. Internal page set identifier for the table space holding the table on which this index was created. The number of entries, including duplicates, in the index space or partition. The number of levels in the index tree. The number of active pages in the index space or partition.
The amount of space in kilobytes that is allocated to the index space or partition. The number of extents used by the index space or partition. The higher part is near the original page if the two page numbers differ by 16 or less. The higher part is far from the original page if the two page numbers differ by more than The timestamp of the last full image copy on the index space or partition.
Each table has a unique index defined on it. The indexes names are:. However, the RTS tables must exist in order for DB2 to externalize the real time statistics that it gathers.
Once the RTS tables have been created and started, DB2 externalizes real-time statistics to the tables at the following times:.
Keep in mind, though, that the default installation uses only a single table space to store both RTS tables.
The default is every 30 minutes. RTS Accuracy. Situations that can cause the real time statistics to be off include:.
The third party utilities should be able both to reset the RTS values and use the RTS stats for recommending when to run utilities. You can specify parameters to indicate to DSNACCOR which table spaces and indexes to analyze, or just run it without parameters to evaluates all table spaces and index spaces in the subsystem.
These recommendations might not be accurate for every installation or subsystem. The following RTS guidelines and queries can be used against to help you identify maintenance and administration that needs to be carried out for database objects in your DB2 subsystems. Because real time statistics are updated in an ongoing manner as DB2 operates, you can use them to see if any activity has occurred during a specific timeframe.
Here is an example checking whether any activity has occurred in the past ten days for a table space just supply the table space name :. The RTS tables contain some good basic information about table spaces.
0コメント