SQL/MX 3.2 Installation and Upgrade Guide (H06.25+, J06.14+)
Table Of Contents
- HP NonStop SQL/MX Release 3.2 Installation and Upgrade Guide
- Contents
- About this manual
- 1 Preparing to install SQL/MX
- 2 Installing SQL/MX
- Summary of installation tasks
- Preinstallation tasks
- Using the InstallSqlmx script
- Installing SQL/MX
- Verifying the SQL/MX installation
- Post-Installation tasks
- 3 Installing a sample database
- 4 Overview of SQL/MX system upgrade
- 5 Considerations for upgrading the system to SQL/MX Release 3.2
- 6 Upgrading the system to SQL/MX Release 3.2
- 7 Falling back from SQL/MX Release 3.2
- A Removing security administrator grants
- B Identifying tables that contain an IDENTITY Column
- C Identifying tables where the ownership has changed
- D Version management and interoperability
- SQL/MX releases
- Interoperability of SQL/MX releases
- Versions of SQL/MX software components
- E Conversions
- Index
Considerations for using the Similarity Check feature
You must consider the following factors before using the Similarity Check feature:
• The DDL_VIEW_SIMILARITY_CHECK defaults attribute is set to ENABLE, by default. In
SQL/MX Release 3.2, if you create a view on a schema with version 1200, 3000, or 3100,
a version-related error is returned. You must set the default attribute to OFF before creating a
view on schemas with a version earlier than 3200.
• If you perform a metadata upgrade on a schema with version 1200, 3000, or 3100 that
contains views, DISABLE SIMILARITY CHECK is added to the view text, and appears in
the SHOWDDL output.
Implementing the new functionality
If there is a chance of falling back to an earlier version, you must defer the implementation of the
new functionality until you are sure that fallback is unlikely.
36 Considerations for upgrading the system to SQL/MX Release 3.2