Page History
...
The following table describes the configurable process parameters and default values in the SQL Server Explain Statements process.
Table 7-29 Configurable 29 Configurable process parameters and their default valuesParameter Default
Parameter | Default value |
---|---|
Explain only the to n batches (based on their In MS-SQL time) |
...
1000 | |
Do not explain statements that were explained in the last n |
...
days | 14 |
About the SQL Server Explain New Statements process parameters
The following table describes the configurable process parameter and default value in the SQL Server Explain New Statements process.
Table 7-30 Configurable 30 Configurable process parameter and its default valueParameter Default
Parameter | Default value |
---|---|
Explain only Top-N batches (based on their In MS-SQL time) |
...
30 |
About the SQL Server Load Data process parameters
The following table describes the configurable process parameter and default value in the SQL Server Load Data process.
Table 7-31 Configurable 31 Configurable process parameter and its default valueParameter Default
Parameter | Default value |
---|---|
Load only Top-N Statements |
...
information |
...
500 |
About the SQL Server Perform SmarTune Analysis process parameters
The following table describes the configurable process parameters and default values in the SQL Server Perform SmarTune Analysis process.
Table 7-32 Configurable 32 Configurable process parameters and their default values
Parameter |
---|
...
Default value |
---|
Check the |
...
following | Findings of Top-N Statements (20) Findings of Top-N Objects (10) History activity for last n days (7) Minimum cost of heavy operators n percent (1) |
Top statements should |
...
have | Minimum In MS-SQL n minutes/hour (1) |
Scalability change for top |
...
statements | Increase in total executions of n percent (10) |
Considered problematic for top |
...
statements | In MS-SQL increased at least by n percent (20) Lock wait time exceeds n percent (10) |
Top objects should |
...
have | Minimum n pages (100) |
...
Minimum IN MS-SQL n minutes per hour (15) |
Major growth of an object defined |
...
by | Increase of n rows (10000) Increase of n pages (20) |
Scalability change for top |
...
objects | Increase in total executions of n percent (10) |
Considered problematic for top |
...
objects | In MS-SQL increased by at least n percent (10) Lock wait time exceeds n percent (20) |
Instance is locked |
...
when | Lock wait time exceeds n percent (10) |
Tempdb is considered a bottleneck |
...
when | Tempdb wait time exceeds n percent (10) |
Buffer cache is considered to be too small |
...
when | Buffer cache hit ratio counter is less than n percent (90) |
...
Number of buffers written by lazy writer is |
...
more than n buffers per second (20) Data pages stay in buffer less than n seconds (300) SQL Server page faults is less than n per second (20) I/O wait time exceeds n percent (5) |
Other applications influence SQL Server memory |
...
resources | SQL Server page faults/sec. exceeds n (20) |
...
Non SQL Server page faults/sec. is less than n (20) |
...
SQL Server memory is less than n percent of total memory (30) |
Other applications influence SQL |
...
Server CPU resources | SQL Server CPU is less than n percent (20) Non SQL Server CPU exceeds n percent (50) Minimum CPU queue length n (2) |
Transaction log is considered a bottleneck |
...
when | Log wait time exceeds n percent (10) |
The average log flushes/sec. is greater than n (100) The average log flush waits/sec. is greater than n (10) Log flush wait time exceeds n minutes per hour (5) |
Statement |
...
Findings | The access plan of the statement contains heavy operators (selected) |
The access plan of the statement has issued a missing indexes warning (selected) Statements accessing the object have missing statistics warnings (selected) The average In MS-SQL time has increased due to a schema change (selected) |
...
The average In MS-SQL time increased due to a growth in statement executions |
...
(selected) |
...
The average In MS-SQL time increased due to a growth in tables (selected) |
The average In MS-SQL time has increased (but the increase is not due to schema changes, table size or scalability) (selected) The total In MS-SQL time of the statement is consistently high (selected) The statement's lock wait time is very high (selected) |
Object |
...
Findings | Statements accessed the object using heavy operators (selected) |
Statements accessing the object have missing indexes warnings in their access plan |
...
(selected) |
Statements accessing the object have missing statistics warnings in their access plan |
...
(selected) |
...
Total In MS-SQL time has increased due to a schema change (selected) Total In MS-SQL time has increased due to a major growth in table size (selected) Total In MS-SQL time has increased due to major growth in total executions of |
...
statements (selected) |
Total In MS-SQL time has increased (but the increase is not due to schema changes, table size or scalability) (selected) The object has unnecessary indexes (containing many updates that are not in use by any SELECT statement) (selected) The object's lock wait time is very high (selected) |
Instance |
...
Findings | Extensive lock wait time (selected) Tempdb is a bottleneck (selected) Buffer cache is too small (selected) Other applications influence SQL Server memory resources (selected) Other applications influence SQL Server CPU resources (selected) The transaction log file is a bottleneck (selected) |
About the SQL Server Purge Internal Data process parameters
The following table describes the configurable process parameters and default values in the SQL Server Purge Internal Data process.
...
Preserve schema change log 6 weeks
About the Sybase Collect Space Utilization process parameters
...
Number of executions over total service time Low
About the Web Load Data process parameters
...
Include only messages that their body met one of the patterns in No default value
Precise. Performance intelligence from click to storage. Learn more > >
...