System database too large

[martinkonicek]

When I go to Symposium -> Configuration -> Historical reports I am unable to change settings because System database is too large.

Are there any way how to shrink database size or increase free space?

 

[Supernn]

Which PEP level are you running?
I've encountered this with SU04 (System database) and that was solved with SU05.
You should go to SU06 with SUS0601-SUS0603

 

[captaingadget]

Assuming the problem is not solved by a PEP update and that the database really is too large, try adjusting the length od time you are keeping historical stats. Interval stats in particular take up a lot of space so work out how long you really need to keep them. Also you may have over stated the call volume i.e. calls per hour, reduce it if it is not realistic.

 

[martinkonicek]

Actually all PBX upgrades was done by some company so I could not find out what is the PEP version we are running but it would be helpfull for me to know the way where this information are shown.

I've tried to calculate size when reduced lenght of time I am keeping historical statistic (32 days) and it would reduce database size but our business need is to keep statistic that time so I could not do that.

When I tried to calculate Calls-per-Hour there is number 100 (system default is 35000).

What helped me was to decrease skillset size - it affect size of database a lot. Unfortunately I am not sure about consequences (call reporting is extremely important to our business and is very sensitive question). So I am attaching word document with screenshot.

Do you think that when we use 135 skilset and I will decrease value from 300 skillsets to 200 skillsets it can negatively affect functionality?

 

[martinkonicek]

Also attaching image for ones who do not want to download word document

 

[captaingadget]

Good move, just keep increasing the value when you run out. Have you tried decreasing the number DNIS, unlikely you will use 10000.

 

[martinkonicek]

That's true that I will unlikely use 10.000 DNIS but when I decrease value from 10.000 DNIS --> 100 DNIS I save about 200 MB of database space (very little effect).

But when I decrease from 350 skillsets --> 200 skillsets I save about 7GB.

 

[Supernn]

Downsizing the amount of skillsets is a good idea.
This has just to do with database allocation. You will not loose any data unless you change the collection period.

The downsizing you're talking about merely implies that as soon as you want to create the 201st skillset you can't.
You can always increase this afterwards.

Please keep in mind that keeping too much data onto the server may cause your server not perform as you should.

We keep the following periods:
Interval: 3 months
Daily: 365 days
Weekly: 52 weeks
Monthly: 36 months
agentlogin: 61 days
CallByCall: 8 days

Just an idea, you do not have to use these of course.
Downsizing these data will cause data to get lost, so please be careful