My History with Infor Visual Manufacturing
When we did our big upgrade to 6.3.8, we moved the database to new hardware and then did the upgrade.
We also had a consultant do the conversion because we moved from Oracle to SQL server.
The conversion went fine. I move copies of the database to my test server all the time. Moving the databases around is no problem since there is no software tied to it directly on the DB server.
I use Microsoft DFS that comes with Server 2003 R2 and beyond to create DFS shares for my visual files. That way I can move servers around and it will not ever break Visual on the desktop.
So my Visual binary files are always loaded from v:\ and the custom reports from o:\.
I also have 3 sites with a WAN, so I use thin clients at the remote sites and a terminal server here connected to my DB server with a Gigabit line. It works great. Much better than running over the wan with just the Visual client.
Even my planners at remote sites use Remote Desktop to run Visual.
Back to the install…
It much easier to do smaller upgrades, so I have done the last 2 by myself.
Like from 6.3.8 to 6.4.1 and then I went from 6.4.1 to 6.5.1.
I upgrade Visual about once a year.
Both upgrades were very simple and the database changes were done in like 15 minutes or less.
I used to use Microsoft SMS 2003 (System Management Server 2003) to push out the software to the desktops, but it was just getting out of hand, so now I run everything from a network share and it seems to be fine.
We have about 50 concurrent Visual users and about 20 barcode stations.
I hate SQLbase. I have to use it for my some of my timekeeping software.
I use Microsoft SQL server 2005 now and it comes with Reporting services free and we use it for lots of custom web based reports. I love it.
The only thing I didn't like was that I had to re-create all my 100 users when I upgraded from SQL2000 to SQL2005. This also happens when you change servers, so I did both things at the same time, so that I would only have to re-create everyone once.