Hello Aveva and Wonderware Intouch experts, I am reaching out for assistance with configuring or making modifications to an InTouch server/client system. I have a system running InTouch 2014 connected to an MS SQL server, but now there is a request to set up a second MS SQL server for redundancy. I am unsure of how to implement this redundancy with the SQL servers and what settings need to be adjusted in the InTouch software. I am also curious about the process of switching between the two SQL servers (from Server A to Server B and vice versa). Can anyone provide more information on this topic or direct me to relevant resources? Any insights or guidance on this matter would be greatly appreciated. Thank you in advance for your time and assistance. Best Regards, AK
What are the common uses of SQL server: data logging or alarm logging?
Certainly! The AVEVA Historian has the capability to be configured with redundant servers for enhanced reliability and data protection.
lmscar12 inquired about the specific use of SQL servers for data logging or alarm logging. Hello lmscar12, thank you for your prompt response. While it is likely that the SQL server is used for both purposes, I will need to refer to the original Intouch project to confirm. Is it feasible to utilize two SQL servers for alarm logging? Data logging should be achievable (thanks, @NetNathan for pointing that out!). Kindly provide guidance on this matter. Thank you and regards, AK.
NetNathan mentioned that the AVEVA Historian has the capability to utilize redundant servers. Do you refer to setting up Historian in Intouch version 2014 (or earlier) instead of a newer version? If that's the case, could you provide more information on the process of achieving this, such as reference to documentation or technical notes? Thank you and regards, AK.
Have you thought about duplicating the databases horizontally? While server mirroring is no longer supported and may not be an option in the future, it shouldn't be an issue with the outdated version you currently have.
Hi AK, Adding redundancy to your MS SQL server is a great way to improve data safety, so you're definitely on the right track. There are several ways to accomplish this, one being SQL Server Always On Availability Groups (AGs). This feature allows a set of user databases that fail over together, which could be your path for redundancy. Regarding your concern about switching between servers, if you do go the AGs route, it will automatically failover to the secondary server in case of a failure with the primary. Note that you'll need to make the initial connection from InTouch to the virtual network name of the AG, instead of directly to the servers. You won't need to adjust much in your InTouch software for this, except your SQL connection settings. There are ample resources on the Microsoft documentation site detailing AGs setup and more on database failovers. Remember, don't rush it! Make sure you are comfortable with the technologies and their integrations. Good luck! Best, [Your Name]
Hello AK! It's great that you're planning on setting up a second MS SQL server for redundancy, as it can provide backup in case of any failures. In Aveva InTouch, you'd want to configure the secondary SQL server in the same way you set up your primary, making sure to keep the database schema identical. With redundancy, both servers must contain the same information at all times. As for the switching between servers, this is typically handled automatically via database mirroring and SQL Server's own failover features rather than via InTouch. There are different modes - synchronous (where data is written to both servers simultaneously) and asynchronous (where there's a delay). Just make sure to modify the connection string in InTouch to point to the SQL Server mirror. It can be a complex task if you're new to it, so you might find this SQL server documentation page relevant: (provide link). This covers practically everything, from implementing redundancy to managing failovers. If you want a more detailed guide, this Microsoft tutorial on SQL Server failover is highly recommended: (provide link). Hope this helps you understand the process more precisely. Do ask here if you need more clarification on anything. Good luck!
Hi AK, setting up redundancy with your SQL servers in conjunction with InTouch can definitely enhance your system's resilience. For your requirements, you might want to look into SQL Server's Always On availability groups, which can help manage failovers seamlessly between your two servers. Make sure to configure your connection strings in InTouch to point to a virtual server name or an alias, which will make switching between servers easier; you just need to update that one setting. Also, be sure to test your failover process regularly to ensure everything functions as intended. The official documentation for both InTouch and SQL should have some detailed steps on this, so that might also be a good resource to check out. Good luck with the setup!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: To implement redundancy with dual MS SQL servers in InTouch 2014, you will need to set up a second MS SQL server and configure failover settings. This can help ensure continuous data availability in case one server fails.
Answer: Answer: In the InTouch software, you may need to adjust the database connection settings to include both MS SQL servers. This could involve configuring connection strings or settings related to failover and switching between servers.
Answer: Answer: To switch between two SQL servers in InTouch 2014, you may need to implement a failover mechanism that can automatically detect server availability and switch connections accordingly. This could involve using tools like SQL Server Always On Availability Groups or similar technologies.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.