Efficiency Tuning of a Daffodil DB / Just one$DB -JDBC Application

0
74
Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  


This short article illustrates the most effective procedures to boost the general performance of Daffodil DB / 1$DB JDBC Driver. This post focuses on how to improve the efficiency of a Daffodil DB / One$DB JDBC application making use of Assertion, PreparedStatemnt, CallableStatement and ResultSet interfaces. Deciding on the appropriate statement interfaces and proper methods according to your SQL query performs a important function in improving the effectiveness of a JDBC Driver.

JDBC Overview

JDBC API offers regular set of interfaces to function with databases like Daffodil DB / One$DB, Oracle, Derby and many others.

Connection interface encapsulates databases connection performance, Statement interface encapsulates SQL assertion representation and execution features whereas ResultSet interface encapsulates retrieving data which will come from the execution of a SQL query making use of Assertion.

Subsequent are the fundamental techniques to create a JDBC method.

1. Import “java.sql” and “javax.sql” offers. (Import “javax.sql”, if highly developed JDBC attribute like XA is to be utilized)

2. Load Daffodil DB JDBC driver (embedded or network JDBC Driver)

3. Build link to database employing Connection interface

4. Build a Statement

5. Execute the Statement

6. Retrieve final results by utilizing ResultSet interface

7. Near Statement and Link

Deciding upon proper Assertion interface:

There are three forms of Statement interfaces in JDBC to signify/execute a SQL query-Assertion, PreparedStatement and CallableStatement. Statement is utilised for executing static SQL statement with no enter and output parameters PreparedStatement is applied to execute dynamic SQL assertion with enter parameters whereas CallableStatement is used to execute dynamic SQL with both input and output parameters. 1 critical thing to observe about PreparedStatement and CallableStatement is that they can also be employed for static SQL statements. Nevertheless, CallableStatement is primarily meant for saved techniques.

PreparedStatement offers greater functionality when as opposed to Statement simply because it is pre-parsed and pre-compiled. This suggests that compilation and parsing of such assertion is completed only at the time by the databases. Afterwards the databases reuses the now parsed and compiled assertion. This significantly improves the efficiency due to the fact each time a assertion has to be executed regularly, it would not will need to be parsed and compiled time and once again. So the overload incurred by parsing and compiling the identical statement can be decreased.

When there is a necessity for single ask for to course of action several complicated statements, CallableStatement gives better functionality as as opposed to PreparedStatement and Statement.

To read through the complete article be sure to stop by [http://www.daffodildb.com/daffodildb-performance-tuning.html]

Source by Parveen Aggarwal

Don't miss out!
Subscribe To Newsletter

Receive top technical news, lesson ideas, travel tips and more!

Invalid email address
Give it a try. You can unsubscribe at any time.

Spread the love
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  
  •  

LEAVE A REPLY

Please enter your comment!
Please enter your name here