32 Bit Support EOL
With QuerySurge's 8.1 release, 32 bit architectures are no longer supported.
The reasons for this transition, we hope, are obvious: computing environments have already migrated to 64 bit architectures in terms of hardware and operating systems. For our users on RedHat Linux, the most recent RedHat version that offers 32 bit support, RHEL 6, has an announced EOL date of 11/30/2020 (see the announcement here for details). From RHEL 7 and beyond, only 64 bit architectures are available. For our users on Windows, Windows Server 2008 was the last version that offered a 32 bit architecture, and its EOL date was 01/14/2020 (as indicated here and here).
- If you have a QuerySurge App server deployed on either 32 bit Windows or 32 bit Linux, you will not be able to upgrade above QuerySurge 8.0.
- If you have a QuerySurge Database server deployed on either 32 bit Windows or 32 bit Linux, you will not be able to upgrade above QuerySurge 8.0.
- If you have any QuerySurge Agents deployed on either 32 bit Windows or 32 bit Linux, you will not be able to upgrade above QuerySurge 8.0.
Important Note: You may have a 32 bit QuerySurge Agent deployed on a 32 bit Windows OS to support querying 32 bit MS Excel or MS Access files via 32 bit Java's JDBC/ODBC bridge. Read on.
If You Use the 32 bit JDBC/ODBC Bridge to Query Microsoft Excel or Microsoft Access
If this is the case, you have two options to choose from:
- You can deploy 64 bit Agents to a 64 bit Windows environment with 64 bit Microsoft Office (with 64 bit ODBC drivers for Excel and Access). However, use of the JDBC/ODBC technology will eventually be deprecated (possibly in the near term) so we don't advise pursuing this approach, as you will have to switch to option (2) when this happens.
- We strongly urge you to switch to a true JDBC-based option. For Excel, you can use QuerySurge's built-in Excel JDBC driver or a commercial JDBC driver for Excel. For Access, you can use either an open-source or a commercial JDBC driver. For more information about Excel, see this FAQ article. For more information about Access, see this FAQ article.