Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

[Imported] period merge of remote clearscada historic points db with local clearscada historic db

EcoStruxure Geo SCADA Expert Forum

Schneider Electric support forum about installation, configuration, integration and troubleshooting of EcoStruxure Geo SCADA Expert (ClearSCADA, ViewX, WebX).

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Remote Operations
  • EcoStruxure Geo SCADA Expert Forum
  • [Imported] period merge of remote clearscada historic points db with local clearscada historic db
Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Top Experts
User Count
sbeadle
Kirk sbeadle Kirk
307
AndrewScott
Admiral AndrewScott
95
BevanWeiss
Spock BevanWeiss
89
AdamWoodlandToo
Lt. Commander AdamWoodlandToo
36
View All
Related Products
product field
Schneider Electric
EcoStruxure™ Geo SCADA Expert

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Solved Go to Solution
Back to EcoStruxure Geo SCADA Expert Forum
Solved
sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2019-11-06 02:57 PM . Last Modified: ‎2023-05-03 12:25 AM

0 Likes
1
974
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2019-11-06 02:57 PM . Last Modified: ‎2023-05-03 12:25 AM

[Imported] period merge of remote clearscada historic points db with local clearscada historic db

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: Roughneck42, originally posted: 2019-04-17 17:23:13 Id:409
we have two pump stations running 5k single clearscada servers. approximately 3k historical points per station. our main plant is running two 25k hot standby clearscada servers with approximately 15k historical points. We would like to merge the pump station historical data up to the main plant scada servers, comms between the two may be interrupted occasionally but is normally a megabit link. I was looking at EWS but this seems to want me to add in every single pump station point individually (groan) I am also worried that ews may be too slow as it seems to use xml.

I'd appreciate some alternative suggestions thanks in advance

Labels
  • Labels:
  • SCADA
Reply

Link copied. Please paste this link to share this article on your social media post.

  • All forum topics
  • Previous Topic
  • Next Topic

Accepted Solutions
sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2019-11-06 02:57 PM . Last Modified: ‎2023-04-25 04:02 AM

0 Likes
0
973
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2019-11-06 02:57 PM . Last Modified: ‎2023-04-25 04:02 AM

>>Responses imported from previous forum


Reply From User: adamwoodland, posted: 2019-04-18 00:03:41
https://community.se.com/t5/Geo-SCADA-Knowledge-Base/Comparison-of-Methods-to-Transfer-Point-Data-Be... might be a good starting point for requirement discussions


Reply From User: sbeadle, posted: 2019-04-18 07:53:02
Ways to make living with a multi-tier system simpler:
1 - use a script to export/import config between tiers and convert object types, setting the properties
2 - use templates on the lower and upper tiers, similar but with the appropriate types. (You can use Template Expressions to set the EWS address property automatically).


Reply From User: du5tin, posted: 2019-04-18 17:23:01
EWS is crazy fast until it isn't. If you try to pull too much historical data it will timeout and crash, then restart. We are starting to use it more for these multi-tiered systems though. For points with minimal historic data it works great and will backfill as required.

Like sbeadle suggests, you can probably export/import, do some sort of bulk conversion to EWS points and then update the tags with a script.


Reply From User: Roughneck42, posted: 2019-04-22 15:56:59
thanks for the response. The comparison table is a good start but how much is too much data when it comes to EWS?


Reply From User: sbeadle, posted: 2019-04-23 16:22:27
'It all depends'!
Allow (say) 50 bytes per value change/time and do a calculation. (This is my guess, I have not looked but it is the right order of magnitude).
Arrange 'scanning' so the client rarely asks for more than 50K of data per point (again, a guess).


Reply From User: du5tin, posted: 2019-04-23 16:41:32
I do not have a good rule of thumb for what is the best configuration. I do know anecdotally that EWS handled syncing history on points that were polled every 30 minutes for a time span of a year without issue (and this was fairly quick!). But we had trouble with facility points that had history records every 2-3 seconds (as some HMIs have) and 6 months of history. We saw high dbserver memory usage on the source system and EWS driver timeouts/freezes on the destination system.


Reply From User: Roughneck42, posted: 2019-04-23 17:48:26
awesome, thanks for the info.

See Answer In Context

Reply

Link copied. Please paste this link to share this article on your social media post.

Reply 1
sbeadle
Kirk sbeadle Kirk
Kirk

Posted: ‎2019-11-06 02:57 PM . Last Modified: ‎2023-04-25 04:02 AM

0 Likes
0
974
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content

Link copied. Please paste this link to share this article on your social media post.

Posted: ‎2019-11-06 02:57 PM . Last Modified: ‎2023-04-25 04:02 AM

>>Responses imported from previous forum


Reply From User: adamwoodland, posted: 2019-04-18 00:03:41
https://community.se.com/t5/Geo-SCADA-Knowledge-Base/Comparison-of-Methods-to-Transfer-Point-Data-Be... might be a good starting point for requirement discussions


Reply From User: sbeadle, posted: 2019-04-18 07:53:02
Ways to make living with a multi-tier system simpler:
1 - use a script to export/import config between tiers and convert object types, setting the properties
2 - use templates on the lower and upper tiers, similar but with the appropriate types. (You can use Template Expressions to set the EWS address property automatically).


Reply From User: du5tin, posted: 2019-04-18 17:23:01
EWS is crazy fast until it isn't. If you try to pull too much historical data it will timeout and crash, then restart. We are starting to use it more for these multi-tiered systems though. For points with minimal historic data it works great and will backfill as required.

Like sbeadle suggests, you can probably export/import, do some sort of bulk conversion to EWS points and then update the tags with a script.


Reply From User: Roughneck42, posted: 2019-04-22 15:56:59
thanks for the response. The comparison table is a good start but how much is too much data when it comes to EWS?


Reply From User: sbeadle, posted: 2019-04-23 16:22:27
'It all depends'!
Allow (say) 50 bytes per value change/time and do a calculation. (This is my guess, I have not looked but it is the right order of magnitude).
Arrange 'scanning' so the client rarely asks for more than 50K of data per point (again, a guess).


Reply From User: du5tin, posted: 2019-04-23 16:41:32
I do not have a good rule of thumb for what is the best configuration. I do know anecdotally that EWS handled syncing history on points that were polled every 30 minutes for a time span of a year without issue (and this was fairly quick!). But we had trouble with facility points that had history records every 2-3 seconds (as some HMIs have) and 6 months of history. We saw high dbserver memory usage on the source system and EWS driver timeouts/freezes on the destination system.


Reply From User: Roughneck42, posted: 2019-04-23 17:48:26
awesome, thanks for the info.

Reply

Link copied. Please paste this link to share this article on your social media post.

Preview Exit Preview

never-displayed

You must be signed in to add attachments

never-displayed

 
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of