Milesprower
Programmer
Has anyone experience with adjusting the historical duration parameters on a live system?
I normally set up new systems so when I adjust them with the customer, there is no impact.
However, I am working on a release 4.2 system that is 24x7. I need to adjust the number of Applications up from 10-15, but the Historical database required size has grown to be larger than its actual size.
So now I am working with the customer to lower the daily and interval duration to get the required size down below the actual size.
I did this on another (release 4,2) live system two years ago and ended up losing data for that day. Is this still an issue?
My guess is that database resizes when daily processing is kicked off @ midnight. As my customer is 24x7 they are concerned about losing data.
I have not found anything in the documentation that addresses issues with reducing the size of the database.
I normally set up new systems so when I adjust them with the customer, there is no impact.
However, I am working on a release 4.2 system that is 24x7. I need to adjust the number of Applications up from 10-15, but the Historical database required size has grown to be larger than its actual size.
So now I am working with the customer to lower the daily and interval duration to get the required size down below the actual size.
I did this on another (release 4,2) live system two years ago and ended up losing data for that day. Is this still an issue?
My guess is that database resizes when daily processing is kicked off @ midnight. As my customer is 24x7 they are concerned about losing data.
I have not found anything in the documentation that addresses issues with reducing the size of the database.