V10 Upgrade Information

Description

This page is dedicated to information for the V10 upgrade process. As we hear or find issues with the upgrade process, we should note them here for others to benefit from.

Findings

Upgrade Logging

I have forwarded this to the configuration management team. They have requested in the past that when we report issues with the installer that we also include the log files -- so going forward (for v10 upgrades), we should use the "Detailed Log" option in the installer where available. When you have issues where there appear to be problems with the installer or with the scripts, please either send them to me with a copy of the log, or enter an RTI incident and attach the log and let me know the incident number.

SQL 2005 Considerations

I am doing an install of 10.2.7 for a re-build of a test environment. A few more caveats about this release have come to my attention. Note that the DB server in this test environment is 64 bit SQL2005. Not a typical situation, but may become more frequent with 10.2.7 and later, 10.2.8, as more clients think about what hardware they are going to want to put in play for a v11.x environment.

Running the DB install (not upgrade, install), after making the connection to the database, the pull down where you would select the respective database names for the install (i.e. Works, IDXwf, Impact) does not provide any database names. The names can be manually typed in, which is fine, but is not how the installation is documented.

Oh, and then the databases are created in name only...NO TABLES! This is a result of where the database backups are unzipped before they are restored. Basically, I think because this is a 64 bit system, there are two Program Files folders: 'C:\Program Files' and 'C:\Program Files (x86)'. So what happens is the installer unzips the database backup to the temp folder in one of these folders and then tries to restore from temp folder in the other one.

.Net TimeZone Issue

The documented location for the script to register the .Net Time Zone code is incorrect. The script that needs to be run is in the following folder:

..\Allscripts Software\TouchWorks\Databases\TW9x_TW10.2.3DBUpgrade\SQL\TouchWorks\Clinical\099 DEC06 Assemby and CLR Procedures for TimeZone.sql

SQL 2005 FW Install Considerations

The setup.hta for IDX Web FrameWork GR 4.09.00.079 is pre-set to SQL2005 = True...this may be an issue if you are not using SQL 2005. The other setup.hta's appear to have this set to False.

Scan Upgrade

For upgrading the Scan database I copied over from live, the dbupgrader was not at all pleased with the patients.viw. I had to drop this view. It was re-created later in the upgrade.