Upgrading to Visual 9

I am currently running 7.1.2 of Visual Manufacturing and I am considering upgrading to 9. Has anyone else been through this upgrade, and if so, and hints or tips on how to have a successful upgrade? Have you been happy with the updated version. Any feedback would be appreciated.

Thank you,

Catherine

0712131256598360.doc

Find more posts tagged with

VISUAL - Enterprise General Discussions

Comments

Legacy Contributor

We are currently on Visual 8.0.0 and wondering the same thing. Hopefully we can get some input from users who are on 9.0.0

VID001_OEET Sourcing_Modify Whse Field to be Enabled.zip

mage.gif

Legacy Contributor

I am preparing to update from Visual 6.5.4 to Visual 9.0.2 this weekend (GULP). It's been a long time coming but the features upgrade will be huge for us.

We worked on plans for the 7.1.2 jump for over a year and then 6 weeks before the upgrade we decided to jump to 9.01.

If you have already done your planning and testing for 8, then changing your plans to 9 is easy. Most of the database upgrade work was for 8 and they do include a database upgrade script that will upgrade you from 7.1.2 to 9 directly allowing the bypass of 8.

Here are some of my upgrade notes for day of upgrade, be sure to read ALL the manuals and take notes like I did here:

All users must perform these steps to upgrade to VISUAL 7.1.2 to 8 or 9:

• Back up the database & Stored Procedures

• Identify and drop custom triggers

• Remove custom indexes

• Review custom tables

• Shrink the database

Backup Server and Database - Disconnect Users

• Make sure everyone is out of Visual (We have a report that show who is logged into the server)

• Email everyone - Tell them to stay off the servers for the next 24hrs.

• Shutdown all your related SQL and Terminal Servers and create VM snapshots in case you need to revert.

• Disable user logins (we did this with a script to keep people out)

• Backup Visual 7.1.2 database to the local disk

• Free up extra drive space and shrink the database (The logs grow during the upgrade)

Upgrade Visual to 9

Additional notes Before / After Vis9 DB upgrade

1. Upgrade the workstation you plant to use for the upgrade to v9 (do not run Visual on the SQL server)

2. To identify custom triggers, use the Examine Triggers function available on the Admin menu in VISUAL.

3. Remove all custom indexes before you upgrade

4. check sql.ini and visual.ini (backup sql.ini and restore after upgrade)

5. Upgrade takes 10 HOURS for a 12GB Database. (We started at 9pm on Friday and let it run overnight)

If your doing this remotely from home on a weekend, refill your beer.

While the upgrade is happening, upgrade your terminal servers and desktops.

6. Turn on trust

7. Recreate triggers in Audit Maintenance.

8. "Fix Synonyms and Grants" will run on its own at the end.

9. Set the SQL compatibility level to the highest level supported in the manual

10. Install Patches (if any)

Legacy Contributor

We upgraded from 7.1.2 to 9.0.1. The only issue we found was in running one of the accounting reports. The uninvoiced receipt report, VFAPIRP9.QRP, gives a divide by zero error, and it should be fixed in 9.0.2.

Visual 9.0.2 has a problem with material planning that is pending defect 622611 resolution. We will not move to 9.0.2 until that defect is resolved.

Through test runs of the database upgrade, some orphaned records were found. After determining that they were not needed they were removed from the 7.1.2 database prior to upgrading.

Legacy Contributor

I am in the process of upgrading from 7.0.0 to 9.0.2 and have ran a test upgrade on a stand alone PC. Like bbidwell78 stated I also ran into some orphaned records in the ECN_OPER_BINARY table and I was able to determine the records were not needed and were removed before further test of the upgrade. We do not have any customization of indexes, tables or triggers so this is not an issue for me. What I do have is that the client machines are running unify 5 for visual 7 and need to be upgraded to unify 7. We have done a little bit of testing and so far have not found any issues. We do have several test to run before setting a cut over date. Probably in then next month or 2.

Elizabeth Scheller-Williams

We upgraded starting November 4th from 7.0.0 sp 3 to 9.0.0. Found orphan purchases, got rid of those. Had an issue with userids porting over to brand new server so had to recreate all of those with permissions. Went from full install on client machines to slim install on client machines with full install on SQL server. Biggest issue was old, old ini files, ended up not bringing them forward and letting software recreating those and users not pre-testing their modified QRP reports.

Unify 5 to 7 advice: Unify will only show up under the admin that installed it so we had to install 5 over 'old' version then that admin could uninstall (with reboot) and then install 7.

rm_benefit_administration_aca_training.pptx

Legacy Contributor

Hi,

Do you recommend the upgrade to 9?

Thanks

have a good day

Nancy

Elizabeth Scheller-Williams

Dear Nancy,

Oh, yes! with the new server we got speed that we desperately needed and the software is much better (at least once everyone got over the change...mostly being the lack of color).

Liz

Copyright © 2025 Infor. All rights reserved.