- What is changing about QuerySurge?
As part of our technology upgrade cycle, QuerySurge is upgrading from Java 7 to Java 8. (Yes, we know, we're pretty late to the party.) Java 8 provides many benefits including enhanced performance and security.
Note: The option to create new Access Connections via Java's builtin ODBC/JDBC is deprecated in QuerySurge version 9.0+.
- Why is this important?
Oracle has removed Java’s built-in JDBC/ODBC bridge component after Java 7. This component is what QuerySurge has used internally to connect to Access files.
- When will I be impacted?
Support for the current method for connecting to Access files is slated to end by October 31, 2019. When you upgrade to QuerySurge 6.4 (or higher), QuerySurge will run on Java 8 or higher (see #1, #2). We have, however, built a backwards compatibility option into QuerySurge to keep your existing Access queries running without change. But: this is a temporary option; we are planning to sunset this feature after October 31, 2019.
- What are my options for my existing Access queries?
Due to the removal of JDBC/ODBC bridge by Oracle, QuerySurge is deprecating the existing Access connection type.
a) Implement (or re-implement) your Access queries with a JDBC Driver for Access (we suggest the open-source UCanAccess driver). There are also commercial drivers available.
b) We understand that users may not be able to switch to a new QuerySurge Access JDBC Driver quickly, so we have built a backwards compatibility option into QuerySurge to keep your existing Access queries running without change. But: if you can’t change over immediately, now is the time to start planning to change over, because we are planning to sunset this feature after October 31, 2019.
- I am an existing user – am I going to be forced to upgrade?
No, of course not. But we’d like to take advantage of newer Java releases that provide new features, better performance and greater security in our product – for you! So we urge you to upgrade as soon as your schedule permits.
- I am an existing user - by what date should I have all my Access queries re-written?
We strongly recommend that you aim to have your existing Access queries rewritten and re-implemented with a new driver by October 31, 2019.
- What will happen to my existing Access queries when I upgrade my QuerySurge?
Your existing queries will continue to run normally - we have built a backwards compatibility option into QuerySurge (see #3, #4). But note: we are planning to sunset this feature after October 31, 2019.
- I’ve heard that Java (which QuerySurge runs on) will soon only be available for a 64 bit architecture. How does this impact QuerySurge?
This is correct – after Java 8, the Java platform only supports 64 bit architectures. QuerySurge 6.4 runs on Java 8, which supports both 32 bit and 64 bit architectures; Java 8 is the final Java version that supports both 32 and 64 bit versions.
- If you have 32 bit QuerySurge components (e.g. Agents) deployed on 32 bit Windows or Linux systems, now is the time to plan for 64 bit replacement systems.
- If you have 32 bit QuerySurge components deployed on 64 bit Windows, these will have to be upgraded to 64 bit QuerySurge.
- When will QuerySurge move beyond Java 8 (i.e., when should I plan to have moved all my QuerySurge components and drivers to 64 bit versions)?
Our tentative end-of-support date is October 31, 2019.
- Will the QuerySurge team be able to help me with the changeover to the QuerySurge Access JDBC Driver (updating queries, connections, etc.)?
QuerySurge Support is always ready to help!
- Regarding Access-related issues and conversions, for standard questions and support issues, your questions can be handled in the usual way, via the QuerySurge Knowledge Base and ticketing system.
- If you feel that you need extra help in your conversion, we’ll be happy to speak with you about a short-term service contract to cover your needs.
Feel free to contact the QuerySurge Support team with any questions or comments through the normal channels or contact us here.