Hi! i'm configuring the history DB for historical data.
I have a lot of point for history ( about 350.000).
what would be the best way to configure?
i don't know if is better a lot of archive managers with few points ( respecting the recommendation of 500Mb for file size) or few archive Managers with a lof of points ( with files size about 1,2-1,7Gb).
What is the option that has the best performance?
The number of Archive Managers in the firtst case is about 70...for me this option is more easy but i don't know the perfomance.
Thanks!
Database Configuration ( History DB)
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Database Configuration ( History DB)
Hello,
how the archive is configured in the best way for your configuration cannot be answered easily.
Therefore you need more detailled information, e.g:
How often are the values changed?
Are you using statistical functions to get compressed values (5-minute-value, daily value, ....)?
How long shall data be available at the project for reporting?
Which type of reporting is used and what is a typical report (e.g. daily values for one month, 5-minute values for one day, ...)?
Can smoothing be used at the archive?
The number of 350.000 dp-elements for archiving seems to be very high.
Are you sure that this number is correct?
Best Regards
Leopold Knipp
Senior Support Specialist
how the archive is configured in the best way for your configuration cannot be answered easily.
Therefore you need more detailled information, e.g:
How often are the values changed?
Are you using statistical functions to get compressed values (5-minute-value, daily value, ....)?
How long shall data be available at the project for reporting?
Which type of reporting is used and what is a typical report (e.g. daily values for one month, 5-minute values for one day, ...)?
Can smoothing be used at the archive?
The number of 350.000 dp-elements for archiving seems to be very high.
Are you sure that this number is correct?
Best Regards
Leopold Knipp
Senior Support Specialist
- xavi.aran
- Posts:63
- Joined: Thu Apr 21, 2011 1:21 pm
Re: Database Configuration ( History DB)
Hi, i attemp to answer your questions:
How often are the values changed? I have 2 type of values, the slow values ( 1-50 times at day) and fast ( 500-1000 times at day). i want to use 1 diferente archive for each type of values
Are you using statistical functions to get compressed values (5-minute-value, daily value, ....)? No, i don't using statistical function.
How long shall data be available at the project for reporting? for fast reporting maybe 2 weeks, and i need to save 2 years the historical data.
Which type of reporting is used and what is a typical report (e.g. daily values for one month, 5-minute values for one day, ...)? Only reports when a incident occurs, is a puntual report, not daily reports.
Can smoothing be used at the archive? Yes, i don't need to save the same values more than 1 time for booleans, and for analog values i use an increment/decrement smoothing
The number of 350.000 dp-elements for archiving seems to be very high.
Are you sure that this number is correct?
Yes, is very high, but this number is correct. We are doing a project for an underground line with 30 stations and all associated devices.
How often are the values changed? I have 2 type of values, the slow values ( 1-50 times at day) and fast ( 500-1000 times at day). i want to use 1 diferente archive for each type of values
Are you using statistical functions to get compressed values (5-minute-value, daily value, ....)? No, i don't using statistical function.
How long shall data be available at the project for reporting? for fast reporting maybe 2 weeks, and i need to save 2 years the historical data.
Which type of reporting is used and what is a typical report (e.g. daily values for one month, 5-minute values for one day, ...)? Only reports when a incident occurs, is a puntual report, not daily reports.
Can smoothing be used at the archive? Yes, i don't need to save the same values more than 1 time for booleans, and for analog values i use an increment/decrement smoothing
The number of 350.000 dp-elements for archiving seems to be very high.
Are you sure that this number is correct?
Yes, is very high, but this number is correct. We are doing a project for an underground line with 30 stations and all associated devices.
- xavi.aran
- Posts:63
- Joined: Thu Apr 21, 2011 1:21 pm
Re: Database Configuration ( History DB)
Can anyone help me in my historyc database configuration?
what would be the best way to configure?
What is the option that has the best performance?
what would be the best way to configure?
What is the option that has the best performance?
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Database Configuration ( History DB)
Hello,
a quick answer to the configuration for the archives in your project is not possible.
When doing the configuration for the archives you need to take several parameters into account, we have not listed all the things you have to think about.
E.g. what data should the customer get when reading values for a long time period, e.g. one month?
How it is prevented that a customer cannot make unusual reports?
If such a report is made for the values which change very often you'll get a huge amount of data.
Also you have to look how many discspace is needed for the storage of values for 2 years.
When archiving such a high number of elements, this will use a lot of disc space.
It would be the best way to discuss these topics directly via mail and/or via phone.
Therefore please get in contact with the ETM sales team for detailled clarification how to proceed in this case.
Best Regards
Leopold Knipp
Senior Support Specialist
a quick answer to the configuration for the archives in your project is not possible.
When doing the configuration for the archives you need to take several parameters into account, we have not listed all the things you have to think about.
E.g. what data should the customer get when reading values for a long time period, e.g. one month?
How it is prevented that a customer cannot make unusual reports?
If such a report is made for the values which change very often you'll get a huge amount of data.
Also you have to look how many discspace is needed for the storage of values for 2 years.
When archiving such a high number of elements, this will use a lot of disc space.
It would be the best way to discuss these topics directly via mail and/or via phone.
Therefore please get in contact with the ETM sales team for detailled clarification how to proceed in this case.
Best Regards
Leopold Knipp
Senior Support Specialist