The db-drivers command is typically useful when you need to perform database data comparisons. This command displays all ADO, ADO.NET, JDBC, and ODBC drivers detected on the local machine. The displayed driver information is INI-file friendly, in the sense that it is in the syntax required for creating database connections in the server or client .ini configuration files, see Setting up Data Sources.
The output of the command is grouped in the following sections:
•ADO.NET - Displays all detected .NET providers
•ADO - Displays all detected ADO providers
•JDBC - Displays all JDBC drivers detected automatically from the CLASSPATH environment variable.
•ODBC - Displays all detected ODBC data source names (DSNs). These are the same data sources that are displayed when you run the ODBC Data Source Administrator (Odbcad32.exe). Note that the 32-bit version of the Odbcad32.exe file is in the C:\Windows\SysWoW64 directory. The 64-bit version of the Odbcad32.exe file is in the C:\Windows\System32 directory.
•Built-in - Displays those database connection methods that have built-in support in DiffDog Server and do not require drivers.
Only drivers that correspond to the platform of DiffDog Server (64-bit or 32-bit) are listed. For example, if the currently installed Java Virtual Machine is 64-bit, the JDBC drivers will be detected only when the command is run by DiffDog Server 64-bit. The same is true for ODBC data source names (DSNs).
This command takes no options or arguments.
On Linux, use an all-lowercase to call the executable. In addition, on Linux and macOS, you might need to add the prefix "./" before the name of the executable when calling it from the current directory of the command shell.
This command can also be called using the list-db-drivers alias. You can use db-drivers and list-db-drivers interchangeably.