 | Loading… |
|
|
|
Performance (analytics console)
    
The Performance panel allows diagnosing issues when the PANTHEON database is running slowly.
User is interested in whether the slow performance is influenced by the internet connection, server issues, or database-related problems.
The functionality is accessed on Database panel in Administration panel.
The following is a description of the functionality of the form.
On the panel, we see a list of databases for which we can perform analyses.
|
Refresh database
|
Update database list on server.
|
|
Analyse
|
The button performs the process of analyzing databases on the server and displays the results on the right side of the form.
|
|
 (Checkbox)
|
The selection of databases that we want to consider is carried out by clicking on the selection field. An orange tick indicates that the database is selected. If there is no tick, the database is not selected.
|
The table displays poorly used indexes for the selected databases.
|
|
The Database filter allows you to display the results of the analysis only for the desired databases on the server. By clicking on the arrow, a list of databases will appear, where by clicking on the selection field we can specify for which databases we want to display the data. 
|
|
Database
|
The name of the database on the server.
|
|
Scheme Name
|
Name of a the schema used.
|
|
Table
|
Table name.
|
|
Index Name
|
Index name. |
|
Index_id
|
ID of the index_id is unique only within the object. |
|
Is_disabled
|
1 = Index is disabled.
0 = Index is not disabled.
|
|
Is_hypothetical
|
1 = Index is hypothetical and cannot be used directly as a data access path. Hypothetical indexes hold column-level statistics.
0 = Index is not hypothetical.
|
|
Has_filter
|
1 = Index has a filter and only contains rows that satisfy the filter definition.
0 = Index does not have a filter.
|
|
Fill_factor
|
> 0 = FILLFACTOR percentage used when the index was created or rebuilt.
0 = Default value
Always 0 for clustered columnstore indexes.
|
|
Total_Writes
|
Number of updates by user queries. This includes Insert, Delete, and Updates representing number of operations done not the actual rows affected.
For example, if you delete 1000 rows in one statement, this count increments by 1.
|
|
Total_Reads
|
Number of seeks by user queries + Number of scans by user queries that did not use 'seek' predicate + Number of bookmark lookups by user queries.
|
|
Difference
|
Difference=Total_Writes - Total_Reads
|
The table displays missing indexes for the selected databases.
|
|
The Database filter allows you to display the results of the analysis only for the desired databases on the server. By clicking on the arrow, a list of databases will appear, where by clicking on the selection field we can specify for which databases we want to display the data. 
|
|
Database
|
The name of the database on the server.
|
|
Index_advantage
|
Number of seeks caused by user queries that the recommended index in the group could have been used for.
Average cost of the user queries that could be reduced by the index in the group.
Average percentage benefit that user queries could experience if this missing index group was implemented. The value means that the query cost would on average drop by this percentage if this missing index group was implemented * 0.01)
|
|
Last_user_seek
|
Date and time of last seek caused by user queries that the recommended index in the group could have been used for.
|
|
DatabaseSchemeTable
|
Name of the table where the index is missing.
|
|
Missing_indexes_for_table
|
Count of missing indexes.
|
|
Similar_missing_indexes_for table
|
Count of similiar missing indexes.
|
|
Equality_columns
|
Comma-separated list of columns that contribute to equality predicates of the form: table.column = constant_value
|
|
Inequality_columns
|
Comma-separated list of columns that contribute to inequality predicates, for example, predicates of the form: table.column > constant_value
Any comparison operator other than "=" expresses inequality.
|
|
User_seeks
|
Number of seeks caused by user queries that the recommended index in the group could have been used for.
|
|
Avg_total_user_cost
|
Average cost of the user queries that could be reduced by the index in the group.
|
|
Avg_user_impact
|
Average percentage benefit that user queries could experience if this missing index group was implemented. The value means that the query cost would on average drop by this percentage if this missing index group was implemented.
|
|
ShortQueryText
|
Short query text.
|
|
TableName
|
Table name.
|
|
TableRows
|
Table rows.
|
The table displays drive level latency information for the selected databases.
|
|
The Database filter allows you to display the results of the analysis only for the desired databases on the server. By clicking on the arrow, a list of databases will appear, where by clicking on the selection field we can specify for which databases we want to display the data. 
|
|
Database
|
The name of the database on the server.
|
|
Drive
|
Operating-system file name.
|
|
VolumeMountPoint
|
Mount point at which the volume is rooted. Can return an empty string. Returns null on Linux operating system.
|
|
ReadLatency_ms
|
Total time, in milliseconds, that the users waited for reads issued on the file/
Number of reads issued on the file.
|
|
WriteLatency_ms
|
Total time, in milliseconds, that users waited for writes to be completed on the file/Number of writes made on this file
|
|
OverallLatency_ms
|
Total time, in milliseconds, that users waited for I/O to be completed on the file/(Number of reads issued on the file + Number of writes made on this file).
|
|
Avg_Bytes_Read
|
Total number of bytes read on this file/Number of reads issued on the file.
|
|
Avg_Bytes_Write
|
Total number of bytes written to the file/Number of writes made on this file.
|
|
Avg_Bytes_REadWrite
|
(Total number of bytes read on this file + Total number of bytes written to the file)/(Number of reads issued on the file + Number of writes made on this file).
|
The table displays calculate average latency for the selected databases.
|
|
The Database filter allows you to display the results of the analysis only for the desired databases on the server. By clicking on the arrow, a list of databases will appear, where by clicking on the selection field we can specify for which databases we want to display the data. 
|
|
Database
|
The name of the database on the server.
|
|
FileName
|
Operating-system file name.
|
|
FileType
|
Description of the file type:
- ROWS
- LOG
- FILESTREAM
- FULLTEXT (Full-text catalogs earlier than SQL Server 2008 (10.0.x).)
|
|
FileSize_MB
|
Current file size, in 8-KB pages. For a database snapshot, size reflects the maximum space that the snapshot can ever use for the file.
 |
HINT
This field is populated as zero for FILESTREAM containers. Query the sys.database_files catalog view for the actual size of FILESTREAM containers.
|
|
|
Avg_Read_Latency_ms
|
Total time, in milliseconds, that the users waited for reads issued on the file/
(1.0 + Number of reads issued on the file).
|
|
Avg_Write_Latency_ms
|
Total time, in milliseconds, that users waited for writes to be completed on the file/(1.0 + Number of writes made on this file).
|
|
Avg_IO_Latency_ms
|
(Total time, in milliseconds, that the users waited for reads issued on the file + Total time, in milliseconds, that users waited for writes to be completed on the file)/(1.0 + Number of reads issued on the file + Number of writes made on this file).
|
| Loading… |
| Loading… |
|
|
|
|