DB SQL query without ODBC - use native DB client

violant · Post by **violant** » Thu Oct 15, 2009 5:34 am

I wish new test that use SQL query without ODBC, but native DB client.
I am not once have error on ODBC test (informix 9.6 - 10 test - every 2 min- small sql query). So I restart HM service and all Ok. I am not sure that problem in ODBC (may be DB client) but I think ODBC let slower SQL test. When next time I get that error I give you more info about problem.
You have DB test but they only test logon/logoff to DB.
Can you do SQL query test without ODBC.

KS-Soft · Post by **KS-Soft** » Thu Oct 15, 2009 11:44 am

Yes, ODBC drivers may work slowly and some of them leads to various problems (e.g. resource leakage).
However ODBC drivers provide uniform interface and can be used for any database. Its hard to support all SQL servers using native clients. Each client provides different interfaces. Even different versions of the same client can be incompatible. and some native clients has "bugs" as well.
Probably we will improve existing Oracle, MS SQL, My SQL... test methods so they will be able to execute SQL query but I think we will not create such tests for different SQL servers (e.g. Informix).

Regards
Alex

violant · Post by **violant** » Fri Oct 16, 2009 10:00 am

Each client provides different interfaces.

So you need to create SQL query test for each DB (MSSQL query, Oracle query...). May be if interface in one DB different - some test for one DB (Oracle 7 query, Oracle 8 query). In options user must put homedir (1:Oracle 10.2.0.2 homedir,2:Oracle 10.2.0.4) and other option like location of configuration file. I use server that have mysql.v4.1.22 and mysql 5.x. I think more custom tuning. HM use not dummer, but IT administrator and he have o lot of knowledge in IT for tunning test.
Almost all DB have alias or you can use your own alias.

some native clients has "bugs" as well.

Almost everytime ODBC use native client for request so if you have bug in it - you have bug in ODBC.

May be later you can add new DB servers

KS-Soft · Post by **KS-Soft** » Fri Oct 16, 2009 11:18 am

So you need to create SQL query test for each DB (MSSQL query, Oracle query...). May be if interface in one DB different - some test for one DB (Oracle 7 query, Oracle 8 query). In options user must put homedir (1:Oracle 10.2.0.2 homedir,2:Oracle 10.2.0.4) and other option like location of configuration file. I use server that have mysql.v4.1.22 and mysql 5.x. I think more custom tuning. HM use not dummer, but IT administrator and he have o lot of knowledge in IT for tunning test.
Almost all DB have alias or you can use your own alias

In this case I am worrying about us, not about administrators. Each database provides different client library, different API, different interface and sometimes they change interface and API. So we have to check and adjust our code for each new version of each database client. While ODBC provides single standard interface.

Almost everytime ODBC use native client for request so if you have bug in it - you have bug in ODBC.

Sure. I did not said ODBC drivers have less bugs than native clients. I am saying that native clients may lead to problems as well.

Regards
Alex

violant · Post by **violant** » Sun Oct 18, 2009 11:06 am

In this case I am worrying about us

You thinking very simple. ODBC it cool and unified, but stable work and perfomance when you get a lot of DB test - it main in enterpriselevel monitoring system. You need have ODBC for some DB SQL query tests and native client DB SQL query for many DB SQL query tests. If you thinking so simple (hard - big work- need to check version)- big company dont buy your product. I warry not about myself but about you.

So we have to check and adjust our code for each new version of each database client.

No you not right. Each new version (if in new version big changes) = new test. Dont rewrite old test. Dont unify DB test - just create new test when you ready for this. Why you afraid to create a lot of test. Create many multilevel folder for DB test (1)DB-1.1)MySQL-1.1.1)MySQL4.1.x-1.1.2)MySQL 5.0.x-1.1.3)MySQL 5.1.x-1.1.4)MySQL 5.4.x). There are two problem when you have a lot of test.
- requirement for test (DB version/build interval or OS version);
- dublicate test (two test for MySQL 4.1.22);
Ok I write many letter so I close this topic because its like spam.

KS-Soft · Post by **KS-Soft** » Mon Oct 19, 2009 12:17 pm

You thinking very simple. ODBC it cool and unified, but stable work and perfomance when you get a lot of DB test - it main in enterpriselevel monitoring system. You need have ODBC for some DB SQL query tests and native client DB SQL query for many DB SQL query tests.

Do you have 1000 ODBC test items? I think nobody have so many ODBC tests. Am I wrong?
If you need to check 10-20 SQL servers, ODBC will work just fine (when ODBC driver and native client are bugs free).

While ODBC logging may slow down system when you use "full" logging mode for 10000 test items. Thats why we plan to implement "native SQL client" logging for most popular SQL servers.

If you thinking so simple (hard - big work- need to check version)- big company dont buy your product. I warry not about myself but about you.
...
Each new version (if in new version big changes) = new test. Dont rewrite old test. Dont unify DB test - just create new test when you ready for this. Why you afraid to create a lot of test. Create many multilevel folder for DB test (1)DB-1.1)MySQL-1.1.1)MySQL4.1.x-1.1.2)MySQL 5.0.x-1.1.3)MySQL 5.1.x-1.1.4)MySQL 5.4.x).

Somehow Microsoft, IBM, Ford and Honda are using our software

Yes, we are thinking differently. We are developing software that should suit big AND small companies as well. If we make things too complicated to support, we will have to increase price. Sure, we can make 100 test methods instead of one and increase price 20 times. Would you like that? I think small firms will not like such idea.

Regards
Alex