Hi There, There is a bit of a gotcha with using Pervasive databases, unless someone is aware of a way around this. It would appear that when the ODBC connection is used that any indexes set up in the Pervasive database are not employed - so a full table scan is used each time. When we tried to pull out just the current months data from a table with a few years history it was the best part of an hour before any rows were returned (as the new rows are at the end of the table). Doing this in the desktop version of QlikView it appears to hang, as the time elapsed is only updated as rows come in, it is also impossible to cancel out cleanly unless rows are being brought in. Regards, Steve.

Hi Ferdinand, This was quite a long time ago now on a client site that I have not been back to for some time. Pie chart with multiple series lovely keynote for mac. We did get the data extracts going at a sensible rate in the end, and I seem to recall that the indexes would be used provided the SQL statement was structured to exactly match the index. For example, make sure the fields in the where clause appear in the same order as they do in the index. Also, if there is a field in an index that you don't want to limit your extract to still put it in the where clause of your statement as Field = '%' - to ensure the index is used.

The requirement for this derives from the fact that the query parser in Pervasive (or maybe just the ODBC driver) is not as intelligent as most RDBMS's and does not work out execution plans very well. If you have serious amounts of data you need to move about and want bespoke drivers then I can recommend speaking to a company called Attunity. Getting data from 'classic' systems is what they are all about. This may be stating the obvious - but if you have slow data transfer from your source system put some thought into QVD usage and incremental loads - search Qlik Communities for more information on this. Hope that helps.

Regards, Steve. Hi Guys, Just quickly I've had some experience connecting to Pervasive databases when supporting a Sage product (Platinum for Windows if that rings a bell.). While the Pervasive server/client ODBC drivers worked reasonably well, we also had a good experience using some old Intersolv (now known as DataDirect I believe) btrieve ODBC drivers. This would work without Pervasive SQL installed and very simple to set up, just needed data dictionary (DDF) files in the relevant data folder). Re performance it seemed to work quite well on large data sets but hard to say if there will be an improvement over Pervasive ODBC drivers. It looks like newer versions are available from DataDirect if you wanted to contact them for more info: '.

4.3 Installing Connector/ODBC on macOS macOS is based on the FreeBSD operating system, and you can normally use the MySQL network port for connecting to MySQL servers on other hosts. Installing the Connector/ODBC driver lets you connect to MySQL databases on any platform through the ODBC interface. If your application requires an ODBC interface, install the Connector/ODBC driver. Applications that require or can use ODBC (and therefore the Connector/ODBC driver) include ColdFusion, Filemaker Pro, 4th Dimension and many other applications. On macOS, the ODBC Administrator, based on the iODBC manager, provides easy administration of ODBC drivers and configuration, allowing the updates of the underlying iODBC configuration files through a GUI tool. The tool is included in macOS v10.5 and earlier; users of later versions of macOS need to download it from and install it manually.

OpenSSL is a required dependency. The macOS installation binaries bundle OpenSSL, while the compressed tar archives do not and require that you install OpenSSL on your system before the installation process. There are two ways to install Connector/ODBC on macOS.

Pervasive 10 Odbc Driver For Mac Pro

Pervasive 10 Odbc Driver For Mac Mac

You can use either the package provided in a compressed tar archive that you manually install, or use a compressed disk image (.dmg) file, which includes an installer. To install using the compressed tar archive (some of the steps below might require superuser privileges). Download the compressed tar archive. Extract the archive: shell tar xvzf mysql-connector-odbc- x.y.z-osx10. Z-x86- (32 64)bit.tar.gz. The directory created contains two subdirectories, lib and bin. Copy these to a suitable location such as /usr/local: shell cp bin/.

/usr/local/bin shell cp lib/. /usr/local/lib. Finally, register the driver with iODBC using the myodbc-installer tool that was included in the package: For Connector/ODBC 8.0: shell myodbc-installer -a -d -n 'MySQL ODBC 8.0 Driver' -t 'Driver=/usr/local/lib/libmyodbc8w.so' For Connector/ODBC 5.3: shell myodbc-installer -a -d -n 'MySQL ODBC 5.3 Driver' -t 'Driver=/usr/local/lib/libmyodbc5w.so' To install using the a compressed disk image (.dmg) file.