Sybase's original proprietary connectivity library was DB-Library, and it has been superseded by CT-Library.
Each database vendor's proprietary connectivity library is typically quite different from those of other vendors. The only exception to this is DB-Library for Sybase versus Microsoft SQL Server, because Microsoft SQL Server was originally derived from Sybase.
Teradata CLIv2 is quite different from Sybase's DB-Library or CT-Library, and it would be a significant amount of work to port an application that uses DB-Library or CT-Library to use Teradata CLIv2 instead. It's certainly NOT a drop-in replacement.
In all honesty, I would strongly recommend converting such an application to use an industry-standard API such as ODBC. It's hard to see any benefit to using proprietary connectivity libraries, because the application must be rewritten in order to switch databases.
↧