unixODBC

[John Jimenez]

In an attempt to reduce overhead on our hp server, installing and using unixODBC was suggested. Our HP/UX system sorts and exports data to our SQL servers. It was suggested unix ODBC would move the proccessing task over to the SQL servers. Could any one expand on this? or give me any pro's and con's on unixODBC?

[Shannon Petry · Accepted solution]

Usually, ODBC is much slower than a direct connection to a database. If your running into performance issues, the last thing you need is a middle layer to make the connection for you. (ODBC is a middle connection that runs on the client but issues SQL commands raw to the server).

Im not sure your setup, so cant make any recommendations. I would suggest that you look at glance and monitor to find bottlenecks. Evaluate a resolution when you find the source of the problem. I.E. If the HP is CPU bound, look at an upgrade. ODBC will not change the CPU usage.

Most people on PC's think that ODBC is better because M$ said so. In reality, most of the time it increases server transaction time and network bandwidth. There is only a benefit of a convenience factor, where a user with an ODBC driver can use the database in several applications. This may or may not be an issue with your database developers.

Regards,
Shannon

[John Jimenez]

shannon,

Thanks for the info. I have ran other ODBC before, and we are already running one now. But this is always from the Database manufacture. I had never heard of this one called "unixODBC"

[Shannon Petry]

There is a product called unixodbc, you can download it from
www.mysql.com

Look for the 3rd party drivers section.

The big catch is that it may or may not work depending on the backside.

Regards,
Shannon