Improving Data Integration with ODBC
How to make ODBC apps work properly?
Successful data integration with ODBC sources depends on many things of which not the least is the performance of ODBC applications. There are several factors that affect ODBC performance. Improvements of those factors help make ODBC applications faster which, in turns, help improve and avoid issues in data integration. Here the factors are:
- Network communication
Reducing network communication may increases ODBC performance multiple times. Arrays of parameters used instead of
INSERTstatements, for example, reduce the time required to complete the operation.
- Choosing the way the transactions are handled
To improve ODBC performance it’s essential to choose the right way transactions are handled. Thus, for example, using manual commits instead of auto-commits gives better control over the work committed.
- Connection pooling
When an ODBC application has several users connection pooling is a good way to increase connection efficiency.
- SQL queries
The efficiency of SQL queries is an important factor affecting the speed of ODBC performance. If something is wrong with it, issues may occur with data filtering causing the driver to get unnecessary data (sometimes the amount of this data is very big) which slows down application performance. Using well-formed and rightly executed queries improves the performance greatly.
ODBC provides good opportunities in data integration, giving an access to multiple data sources through one application. So keeping the application’s performance high will benefit the process of data integration.
Now with Apatar
The Apatar team has recently released the connector for ODBC sources, something that plenty of our users have been asking and waiting for. The fact that the connector was quite highly demanded kind of argues the talks heard for about couple of years of ODBC being an old and forgotten means of accessing databases.
Well, actually, we have created the connector for ODBC to ease and improve data integration for Apatar users. ODBC remains widely used in organizations and enterprises. As any technology, it has its pros and cons, of course.
The main ODBC’s advantage is its universality—having appropriate drivers for a connection, users may access different databases they need. So, in fact, the connector for ODBC sources allows perform needed operations on data exactly in the sources user’s ODBC has access to. In other words, Apatar may lack a connector for a database, but as soon as this database is among user’s ODBC sources, the user may integrate or synchronize data from this source with the data from other sources.
So I think, the creation of the connector for ODBC sources, positively, was a great thing which may help users in their data integration and ETL initiatives.
“I have downloaded and tested a lot of ETL products (all open-source), and Apatar was the only one that worked at the first strike (no server side needed, no problem with the Oracle JDBC).” —Andrea Ronchese, Integrated Management System Manager, S.A. Giuseppe Cristini S.p.A.