[ZBXNEXT-3461] Add more robust ODBC monitoring options. Created: 2016 Sep 27  Updated: 2016 Sep 27

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.2.14
Fix Version/s: None

Type: Change Request Priority: Major
Reporter: Sandis Neilands (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: odbc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

See ZBX-8489 -> ZBX-11213.

There are several risks related to the direct use of the ODBC API. Mainly - there is too much allowed variety. The driver developers can target different ODBC levels, implement different subsets of the API, interpret the API requirements differently. In addition, there can be mistakes in both our code and driver code.

As a mitigation for these risks (e.g. workaround) we could introduce hidden (by default) configuration parameters:

  • use isql binary directly instead of ODBC API;
  • user configurable maximum field width (e.g. revert changes for ZBX-8489 and use user-configured size in SQLBindCol() instead of MAX_STRING_LEN).

Generated at Fri Mar 29 02:55:25 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.