2007-08-22 MonitorWare Agent 5.0 Final Released

Wednesday, August 22nd, 2007

MonitorWare Agent 5.0 Released

Adiscon is proud to announce the 5.0 release of MonitorWare Agent. A prime focus of this release is on reliability. That, of course, not just meaning proper program execution but on delivering messages even under bad circumstances. Circumstances, that other solutions may not even be aware of, much less are capable to handle. Main new features include: (more…)

2007-08-22 MonitorWare Agent 5.0 Final (Build Service 5.0.336/Client 5.0.1161)

Wednesday, August 22nd, 2007

MonitorWare Agent 5.0 Released

Build-IDs: Service 5.0.336, Client 5.0.1161

New Additions

  • Forward Syslog Action– Added support for sending multiple messages over a persistent syslog/TCP connection.
    – Added capability to force -transport-tls like octet-counted framing for syslog/TCP connections.
    – Added a new major feature into this Action, Diskqueue. This new option is only available for TCP based Syslog. Whenever a connection to a remote syslog server failes, the action starts caching the syslog messages in a local temp file. The folder for these files can be configured. You do not need to worry about multiple Actions using this feature, the filenames are generated using a unique GUID which is automatically generated for each Action. (more…)

ODBC on x64-Machines

Tuesday, August 7th, 2007

ODBC on x64-Machines

Article created 2007-09-07 by Rainer Gerhards.

Microsoft provides integration of 32bit software into the 64 bit world. They have worked quite hard to make any differences invisible to the user and even the programmer. However, there are some subtleties that cannot be totally hidden. One of them can be experienced in the ODBC subsystem.

There are actually two ODBC subsystems in 64bit-Windows – one for the 64 bit world and one for the 32 bit world. This is necessary, because there were a number of changes that prevented 32 bit drivers from running in the 64 bit environment. In general, these two worlds are quite transparent to the user. However, there are some restrictions:

  • Drivers can not be shared between worlds. Most importantly, that means that many ODBC drivers (e.g. JET) are not available to 64 bit ODBC programs
  • Changes to the ODBC configuration made with 32 bit tools affect only the 32 bit world – and vice versa

In practice, these two restrictions limit the utility of ODBC on 64 bit Windows versions. This comes at no surprise, given that MĂ­crosoft has declared ODBC to be legacy some years ago and is actively promoting OLEDB (where there is a rich choice of drivers available).

When working with ODBC, please keep these restrictions on your mind. For best results, we recommend using OLEDB functionality, which is available in Adiscon products. OLEDB also offers a better performance.