Versions Compared

Old Version 8

changes.mady.by.user Emma Fullilove (Deactivated)

Saved on

compared with

New Version Current

changes.mady.by.user Emma Fullilove (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

  1. Disable replication,

  2. Update the primary database and following all the steps below

  3. Re-do Step 4 for each subscriber database.

  4. After all databases have been updated, then you may reenable replication.

*

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:

...

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

...