HP 3PAR StoreServ 7200 2-node HP 3PAR System Reporter 3.1.0 Software User& - Page 114

Compacting Databases

Page 114 highlights

Table 54 Sampling Policies (continued) Policy Default Default number of hours to keep hi-res samples (in force by default for all systems 24 unless specified otherwise on an individual basis) Default number of days to keep hourly samples (in force by default for all systems 7 unless specified otherwise on an individual basis) Default number of days to keep Adaptive Optimization hourly samples (in force 7 by default for all systems unless specified otherwise on an individual basis) Default number of days to keep daily samples (in force by default for all systems 366 unless specified otherwise on an individual basis) Ratio of Hi-Res performance samples to Hi-Res space samples. 6 Typically space changes are slower than performance so space sampling can be configured at a slower rate than performance sampling. Perform compaction of the database after next sample (SQLite only. Sampling will be stopped and database will be unavailable for several minutes) see "Compacting Databases" (page 114) daily If there is a problem with sampling, send email to this address. (blank) Email is only sent if the sampling problem requires the sampler service/daemon to exit. Compacting Databases When some sampling policies are changed or when the number or sizes of systems being sampled is reduced the size of the database may be reduced significantly. If a MySQL or Oracle database is being used and there is a significant change in size, the database's tables do not automatically shrink. A compaction must be performed on the database in order to recover the file space. To start a compaction on the database, change the policy labelled Perform compaction of the database after next sample to now, daily or to the specific day of the week depending on whether you want to perform the compaction now, immediately after each daily sample or immediately after the daily sample on the specified day of the week. If the policy value is set to now the compaction is done once and the value is automatically reset to 0. To achieve compaction with MySQL databases, System Reporter uses the OPTIMIZE command. For Oracle databases System Reporter uses the ALTER TABLE SHRINK SPACE command. See your SQLite, MySQL or Oracle database documentation for further information about database compaction using these commands. For MySQL and Oracle databases, compaction is done by an external process so that data sampling can continue in parallel with database compaction. However, for SQLIte databases sampling is suspended until the compaction is complete. For MS SQL, the compaction is performed using the following procedure: DBCC SHRINKDATABASE ( database_name [ , target_percent ] [ , { NOTRUNCATE | TRUNCATEONLY } ] ) DBCC SHRINKFILE ( { file_name | file_id } { [ , target_size ] | [ , { EMPTYFILE | NOTRUNCATE | TRUNCATEONLY } ] 114 Configuring the System Reporter Policy Settings

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231

Table 54 Sampling Policies
(continued)
Default
Policy
24
Default number of hours to keep hi-res samples (in force by default for all systems
unless specified otherwise on an individual basis)
7
Default number of days to keep hourly samples (in force by default for all systems
unless specified otherwise on an individual basis)
7
Default number of days to keep Adaptive Optimization hourly samples (in force
by default for all systems unless specified otherwise on an individual basis)
366
Default number of days to keep daily samples (in force by default for all systems
unless specified otherwise on an individual basis)
6
Ratio of Hi-Res performance samples to Hi-Res space samples.
Typically space changes are slower than performance so space sampling can
be configured at a slower rate than performance sampling.
daily
Perform compaction of the database after next sample (SQLite only. Sampling
will be stopped and database will be unavailable for several minutes)
see
“Compacting Databases” (page 114)
(blank)
If there is a problem with sampling, send email to this address.
Email is only sent if the sampling problem requires the sampler service/daemon
to exit.
Compacting Databases
When some sampling policies are changed or when the number or sizes of systems being sampled
is reduced the size of the database may be reduced significantly.
If a MySQL or Oracle database is being used and there is a significant change in size, the
database’s tables do not automatically shrink. A
compaction
must be performed on the database
in order to recover the file space. To start a compaction on the database, change the policy labelled
Perform compaction of the database after next sample to
now
,
daily
or to the specific day of the
week depending on whether you want to perform the compaction now, immediately after each
daily sample or immediately after the daily sample on the specified day of the week.
If the policy value is set to
now
the compaction is done once and the value is automatically reset
to 0.
To achieve compaction with MySQL databases, System Reporter uses the OPTIMIZE command.
For Oracle databases System Reporter uses the ALTER TABLE SHRINK SPACE command. See your
SQLite, MySQL or Oracle database documentation for further information about database
compaction using these commands.
For MySQL and Oracle databases, compaction is done by an external process so that data sampling
can continue in parallel with database compaction. However, for SQLIte databases sampling is
suspended until the compaction is complete.
For MS SQL, the compaction is performed using the following procedure:
DBCC SHRINKDATABASE
( database_name [ , target_percent ]
[ , { NOTRUNCATE | TRUNCATEONLY } ]
)
DBCC SHRINKFILE
( { file_name | file_id }
{ [ , target_size ]
| [ , { EMPTYFILE | NOTRUNCATE | TRUNCATEONLY } ]
114
Configuring the System Reporter Policy Settings