SQL Server
SqlServerCPUAlert
The execution of a reference calculation on the SQL server took too long. The calculation consists in incrementing a variable from 1 to 1 million.
Context (JSON) | Comment |
|---|
CpuSpeedTestDuration | Observed execution time |
RepositoryHealthSQLCompatibiltyLevelAlert
SQL data format is not aligned with your SQL Server version.
It is highly recommended not to work with a data structure version older than the SQL server one.
Context (JSON) | Comment |
|---|
Version | Version number of your SQL server |
Compatibility | Version number of your SQL data (Compatibility level) |
RepositoryHealthSQLPrivateWorkspaceAlert
The RemovePrivateWorkspaceTempData stored procedure has never been performed or was performed more than 7 days ago.
The RemovePrivateWorkspaceTempData stored procedure must be performed at least once a week.
Context (JSON) | Comment |
|---|
Lastexecution | Last execution time or “never” |
RepositoryHealthSQLHistoricalDataAlert
The ShrinkUnusedHistoricalData stored procedure has never been performed or was performed more than 7 days ago.
The ShrinkUnusedHistoricalData stored procedure must be performed at least once a week.
Context (JSON) | Comment |
|---|
Lastexecution | Last execution time or “never” |
RepositoryHealthSQLTableAlert
The RemovePrivateWorkspaceTempData stored procedure has never been performed or was performed more than 7 days ago.
The RemovePrivateWorkspaceTempData stored procedure must be performed at least once a week.
Context (JSON) | Comment |
|---|
Lastexecution | Last execution time or “never” |
RepositoryHealthSQLIndexAlert
An index fragmentation exceeds 50%.
An SQL maintenance plan must be performed at least once a week.
Context (JSON) | Comment |
|---|
Table | Table name |
Index | Index name |
Ratio | Fragmentation percentage |
Daily measures of data access performances
RepositoryPerformanceROGraphCommentReadAlert
Reading of 1000 existing large objects (BLOB). This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |
RepositoryPerformanceROGraphReadAlert
Existing graph exploration (1000 objects and 500 MetaAssociations).
This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |
RepositoryPerformanceROGraphQueryAlert
ERQL queries on existing graph (1000 objects and 500 MetaAssociations).
This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |
RepositoryPerformanceRWGraphCommentWriteAlert
Writing of 1000 large texts (BLOB).
This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |
RepositoryPerformanceRWGraphCreateAlert
Creation of a graph including 1000 objects and 500 MetaAssociations.
This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |
RepositoryPerformanceRWGraphDestroyAlert
Deletion of a graph including 1000 objects and 500 MetaAssociations.
This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |
RepositoryPerformanceRWGraphQueryAlert
ERQL queries on a recently created graph (1000 objects and 500 MetaAssociations).
This test execution time is higher/lower than the reference time calculated for the last 30 executions. An event of this type may be due, for example, to:
the CPU load and/or the server memory available at test execution time (4 pm GMT)
an infrastructure change (e.g.: network, VM size, hardware)
the SQL repository maintenance plan execution time, which is too old
a cache configuration change (e.g.: Redis, cache file)
anti-virus policy
Context (JSON) | Comment |
|---|
Performance | Test execution time (in ms) |
Comparedtoaverage | Current measure characterization according to the standard measure |