How can I access the old single-threaded database engines?

Nico Chart_21517
Nico Chart_21517
Altair Employee

In the upgrade from version 3 to version 4 and version 2023 of Altair SLC, a new set of multithreaded database engines were introduced. Multi-threaded engines are able to work faster by carrying out multiple database interactions at the same time.

The non-threaded (single-threaded) engines were retained and the single-threaded engine has the original name with OLD appended; for example, SQLSERVEROLD.

The engine names are:

Multithreaded      Legacy

NETEZZA            NETEZZAOLD

ODBC               ODBCOLD

ORACLE             ORACLEOLD

SQLSERVER          SQLSERVEROLD

System Options:

These system options enable you to tell SLC to fall back to using the legacy version of a database engine if necessary. They are only specifiable on the command line or in the config file as it doesn't make sense to be able to do it in code – nor could it work that way.

The options take the form legacy<enginename>engine, so:

legacydb2engine
legacynetezzaengine
legacyodbcengine
legacyoracleengine
legacysqlserverengine (legacysqlsvrengine and legacysqservrengine will also work as aliases)

These have the effect of changing a libname by appending "old" on the end before loading and invoking the engine.

 

Tagged: