|
Posted
over 9 years
ago
by
ritchiecarroll
Yes - as many inputs as you would Renan - from any number of sources...
|
|
Posted
over 9 years
ago
by
ritchiecarroll
Yes - as many inputs as you would Renan - from any number of sources...
|
|
Posted
over 9 years
ago
by
ritchiecarroll
This is not RDBMS based - it used a relational database only to store "meta-data" about the points being archived.
The system is designed for high-speed time-series data storage - with a very efficient data storage size footprint.
|
|
Posted
over 9 years
ago
by
ritchiecarroll
This is not RDBMS based - it used a relational database only to store "meta-data" about the points being archived.
The system is designed for high-speed time-series data storage - with a very efficient data storage size footprint.
|
|
Posted
over 9 years
ago
by
ritchiecarroll
Fail over cluster is not an issue - you can setup an assigned shared drive that will follow the active cluster...
Be happy to discuss further...
Thanks,
Ritchie
|
|
Posted
over 9 years
ago
by
ritchiecarroll
Fail over cluster is not an issue - you can setup an assigned shared drive that will follow the active cluster...
Be happy to discuss further...
Thanks,
Ritchie
|
|
Posted
over 9 years
ago
by
ritchiecarroll
That would be possible, but take some time. How about Mono?
Ritchie
|
|
Posted
over 9 years
ago
by
ritchiecarroll
That would be possible, but take some time. How about Mono?
Ritchie
|
|
Posted
over 9 years
ago
by
ritchiecarroll
Important Note
Source code for this project has been migrated to GitHub: https://github.com/GridProtectionAlliance/openHistorian
All new source code and product releases will be posted there.
Project Description
The openHistorian
|
|
Posted
over 9 years
ago
by
ritchiecarroll
Important Note
Source code for this project has been migrated to GitHub: https://github.com/GridProtectionAlliance/openHistorian
All new source code and product releases will be posted there.
Project Description
The openHistorian administered by
|