...
| Info |
|---|
Regarding SQL Replication: If you are using SQL redundancy and you are replicating all objects, you only need to update the primary database and SQL replication will take care of updating all redundant servers. If you are only replicating a few objects you will need to disable
|
| Note |
|---|
SQLUpdate_37 modifies the primary key of tblItems. If you are only replicating a few objects and one of those objects will be updated by the ACM Sql Scriptsthis table and upgrading from DB version 36 or lower to DB Version 37 or higher, you will need to remove it as an article of replication, perform the update and then add it back. Instructions are here: Remove and Add a Table as an Article of Replication |
Step 1: Stop all ACM Services:
...
Disconnect all HMI’s and OPC Clients from ACM to prevent asiData from being restarted
Stop all ACM services in the ACM Monitor on the Status tab.
Exit ACM Monitor from the Task Tray by right clicking the ACM Monitor icon and selecting “Exit”.
...
Step 2: Back up the ACM SQL database:
...
| Info |
|---|
The installer references the asiDATA.ini file for the saved database information. If a connection to the database can be made, the installer will examine the ACM database version and prompt for permission to update the database if needed. You can use the installer to update your current database or you can choose to update your ACM database manually following Step 5. |
Follow steps 1-19 13 detailed on the Installation guide.
If you allowed the installer to update the database, and you are not replicating OR you did not have to turn off replication, you are done! Otherwise continue to Step 5 4 to upgrade the database.
Step
...
4: Upgrade the ACM Database
If you elected not to upgrade the database via the installer or if you are using replication and had to disable it, perform the following on each subscriber/redundant database.
...