25 Jan 98
Upgrades must be from 6.x. 4.2 must be upgraded to 6.x first.
Can be done on one machine or onto a different machine.
Replication allows all combinations of 6.0, 6.5 and 7.0 to work together. Servers involved in replication can be upgraded in any order but a separate distribution server must be upgraded first.
The upgrade is managed with a wizard.
Upgrade speeds (using a server-server pipeline, not tape, which is also supported):
1G -- < 1 hour
10 G -- < 4 hours
50 G -- < 12 hours
100G -- < 24 hours
Microsoft reports that upgrading their 80GB SAP server took 14.5 hours. If you use tape, it will take roughly twice as long.
A compatibility mode will be automatically set for 6.x databases. This will
Prevent keyword conflicts
Have an implicit ORDER BY for GROUP BY
Provide 6.x treatment of empty strings
Replicate an obscure bug in the UPDATE statement
Most upgrade problems to date have been
Applications which made direct access to system tables 17%
Problems already present in user objects which were manifest when the object was upgraded 6%
No other problem has appeared in more than 1% of the tests
Many thanks to Sharon for providing these notes - drop her a note at firstname.lastname@example.org and tell her thanks!