Click on the "Run All" button if you would like all the different benchmark type combinations to be performed.

When benchmark run complete benchmark data is written to the benchmark program's output pane.

Figure15.12.

The key pieces of benchmark data that you need to look out for are:

Total Transactions. total number of transactions completed during the benchmark run

Transactions Per Second. number of transaction completed per second for the benchmark run

Information from this benchmark is automatically written to an Excel format CSV (the file c:\odbcbnch.csv) which makes it easy for you to graph and pivot data collated from several benchmark runs. A later version of this demo will actually write the benchmark data into an ODBC DSN that you provide thereby offering even more flexibility and accessibility to benchmark data.

Run the script openlink.sh to set up your environment:

openlink.sh

Start ODBCTEST by executing the following command:

odbctest

Or pass a DSN connect string, for example:

odbctest DSN=marketing;UID=name;PWD=pwd;

At the SQL command prompt enter "?" for a list of ODBC DSNs on your machine or enter a valid ODBC Connect String e.g.

If you have a DSN named "Marketing" you would enter: DSN=Marketing

Open a Terminal session, and start ODBCTEST by executing the following command:

/Library/iodbc/bin/odbctest

At the SQL command prompt enter "?" for a list of ODBC DSNs on your machine or enter a valid ODBC Connect String. If you have a DSN named "Marketing" you would enter:

DSN=Marketing;UID=username;PWD=password

Note: If there is no password, you must include a semicolon at the end:

DSN=Marketing;UID=sa;PWD=;

Any valid SQL or ODBC command may be executed through this interface. The following example shows a connection to Microsoft SQLServer 2000, making a simple query against the sample Northwind database:

[localhost:~] openlink% /Library/iodbc/bin/odbctest
iODBC Demonstration program
This program shows an interactive SQL processor
Enter ODBC connect string (? shows list, or DSN=...): DSN=user_tthib_sql2k
SQL>select au_lname, au_fname, state from authors where au_id < '333-33-3333'
au_lname                                |au_fname            |state
----------------------------------------+--------------------+-----
White                                   |Johnson             |CA
Green                                   |Marjorie            |CA
Carson                                  |Cheryl              |CA
O'Leary                                 |Michael             |CA
Straight                                |Dean                |CA
 5 row(s) fetched.
SQL>quit
Again (y/n) ? n
Have a nice day.
[localhost:~] openlink%

Go to the OpenLink Data Access Drivers "Start Menu" program group and then follow the JDBC Samples menu path to the appropriate JDK, and then JDBCDemo. This will execute a DOS batch program that initialises the Java demo application.

Figure15.13.JDBC Demo

Set the JDBC Driver Name and URL settings for the connection to your database. The "Driver Name" field identifies the jdbc Driver. The "Connection URL" field requires a valid JDBC URL.

Figure15.14.JDBC Demo

Enter a valid SQL statement and then click the "Query" button, the example below uses a SQL statement requesting all records from the "Customers" table.

Figure15.15.JDBC Demo

Go to the OpenLink Data Access Drivers "Start Menu" program group and then follow the JDBC Samples menu path to the appropriate JDK, and then Rowset Demo. This will execute a DOS batch program that initialises the Java demo application.

Figure15.16.Rowset Demo

Set the JDBC URL settings for the connection to your database. The "Connection URL" field requires a valid JDBC URL.

Figure15.17.Rowset Demo

Enter a valid SQL statement and then click the "Query" button. The first rowset of the resultset will be shown.

Figure15.18.Rowset Demo

Click on the "Next" button to retrieve the next rowset, "Prior" to go back a rowset, "First" to move directly to the first rowset, and "Last" to move to the last rowset.

"Delete", "Refresh", "Lock", "Unlock", "Add" and Update" work on the principle of a current row in the rowset. To indicate the current row to the applet, you must click on any column of a particular row and then press a key. The status panel will then display "Current Row = 2" or similar, indicating that the current row is set.

Clicking "Delete" will attempt to delete the row from the database. Clicking on "Refresh" will now retrieve the latest values from the database to refresh that row. However this may not be successful dependent on the restrictions place on the resultset by the underlying database.

"Lock" and "Unlock" will attempt to perform those operations on the current row, which again, may or may not be successful, dependent on the restrictions of the underlying database.

"Add" will attempt to add the contents of the current row as a new row to the relevant tables forming the resultset. "Update" will attempt to update the modified contents of the current row to the database. Again the success of these two operations depend on the restrictions placed on the underlying database.

"Get Bookmark" will attempt to retrieve a bookmark for the current rowset position, which "Set Bookmark" will attempt to return to.

To move to a particular position in the resultset, enter that position into the edit box next to the "Goto" button and click the "Goto" button.

Go to the OpenLink Data Access Drivers "Start Menu" program group and then follow the JDBC Samples-->ScrollDemo2 (JDK1.2) menu path, this will execute a DOS batch program that initializes the Java demo application.

Figure15.19.

Set the JDBC Driver Name and URL settings for your connection to a database of your choice. The "Driver Name" field identifies the OpenLink Driver. If it is left blank, then it defaults to "openlink.jdbc2.Driver", which is the OpenLink Driver for JDBC 2.0. The "Connection URL" field requires a valid OpenLink JDBC URL.

Figure15.20.

Enter a valid SQL statement and then click the "Query" button.

Figure15.21.

You can now use the navigational buttons to Scroll backwards and forwards, each of these navigational buttons highlights OpenLink's full implementation of the JDBC 2.0 Scrollable Cursors specifications.

Start the OpenLink Admin Assistant and then follow the Sample Applications-->JDBC Applet Demos menu path.

Figure15.22.

Click on the "ScrollDemo2" hyperlink which initializes the ScrollDemo2 applet, if you do not have a Java 1.2 or Java 2.0 compliant browser you will not be able to run this Applet demo. The other way to experience this demo is to run the Application version which uses your operating systems Java Virtual Machine (JVM) instead of a JVM inherently linked to a Web Browser.

Go to the OpenLink Data Access Drivers "Start Menu" program group and then follow the JDBC Samples-->Jbench (for JDK1.1 1.2 or 1.3) menu path, depending on the JVM you have installed. This will execute a DOS batch program that initializes the JBench application.

Figure15.23.

The follow the File-->Connect menu path to make your initial connection. You will need to identify your JDBC Driver (by providing appropriate Driver Name values in the JDBC Driver field) and then provide a valid JDBC URL for your specific JDBC Driver.

Figure15.24.

Select the open JDBC connection that you wish to test.

Follow the TPC-A-->Load Tables menu path to prepare your database for the TPC-A benchmark, select a database schema type that matches the database engine that you are benchmarking. If your database isn't listed ANSI should suffice (as long as this is an ANSI SQL compliant database).

Figure15.25.

Follow the TPC-A-->Load Procedures menu path to Load the TPC-A stored procedures.

Now that all the benchmark data and stored procedures have been loaded into your database, follow the TPC-A-->Run Benchmark menu path and then configure your actual benchmark session parameters:

The benchmark parameters fall into 4 categories, Bench execution mode, Run Options, SQL Options, and Execution Options.

Figure15.26.