When database client applications communicate with a database server they make API calls to a database client library (DCL) providing database communications API. For Microsoft SQL Server and Sybase SQL Server, up to release 4.9, this library was DBLIB. In Windows 3.1/3.11 DBLIB is the DLL named W3DBLIB.DLL. For Windows 95/Windows NT the DBLIB library name is NTWDBLIB.DLL. For Sybase SQL Server System 10 and 11 Sybase introduced 2 new client libraries: CTLIB and SYBDB. For CTLIB the name of the DLL for Windows 3.1/3.11 is WCTLIB.DLL, for Windows 95/Windows NT the DLL is LIBCTLIB.DLL. For SYBDB the respective names are WSYBDB.DLL and LIBSYBDB.DLL. SYBDB API is very similar to DBLIB API except for several function declarations.

Client applications make calls to DCL to communicate to a database. 3GL-written applications, such as "C" or "C++", usually make these calls explicitly(if not using database class libraries), while 4GL-written applications, such as written in Visual Basic or PowerBuilder, usually make these calls implicitly, through programming constructs provided by the 4GL. The task of tracing database calls the application is making becomes very important for:

The DBSPY 2.0 program requires the following minimum hardware and software configuration:

DBSPY 2.0, 16-bit edition can also run as a 16 bit application under Windows 95 and Windows NT operating systems. In this case it has to run NOT in separate memory space and will trace calls from the 16-bit applications running NOT in separate memory space.

The installation procedure has to be used in order to install the program. You cannot simply copy the program files from the installation disk to your hard drive.

Insert the Installation Disk into a floppy drive.

From the MS Windows Program Manager or File Manager starts the SETUP.EXE program from your floppy drive (A: or B:).

Follow the installation instructions in your screen.

To start the program click on the DBSPY 2.0 icon:

You can also run the DBSPY16.EXE (for 16-bit edition) or DBSPY32.EXE (for 32-bit edition) from Program Manager or File Manager.

The start-up screen has one open empty sheet:

For each client library (DBLIB, CTLIB, SYBDB) you can select a number of functions that you want to trace, tracing presentation attributes such as: application name, arguments, timing and logging. Also you will have to select process(es) (application(s)) that will be traced.

To turn the trace ON you will have to make the following selections:

Tracing Options window will be displayed:

To select database library for tracing click on the respective tab (DBLIB, CTLIB, and SYBDB) on the tab folder in the Tracing Options window.

In order to select a function for tracing you have to move it from the ‘Available’ box to the ‘Selected’ box.

Selecting a function to trace can be done in several ways:

Drag a function from the left selection panel (‘Available’ box) and drop it into the right panel (‘selected’ box).

Select a function or a group of functions (extended selection using Shift or

Control Keys) and click on button.

‘Available’ box to ‘Selected’ box.

Unselecting functions is similar to selection, except that all transfers are from the right panel (‘selected’ box) to the left panel (‘Available’ box).

Example: To unselect all function(s) click on button.

In order to select application(s) that will be traced you have to make a single or multiple selection in the list box: Processes located in the left bottom part of the Tracing Options screen.

To select presentation attributes for trace information use the box in the right-hand bottom part of the Tracing Options Screen. It lets you specify whether API call arguments, application name from which the call has been made, return code and execution time for the call should be presented in the trace view. You can also specify if and where the tracing information should be logged.

These settings affect only the visible presentation of the trace in the main tracing window. For detail information on the traced call, logging and file operations all trace attributes are used.

To show arguments in the main tracing window click on ‘Arguments’ check box.

To show function execution time (seconds) in the main tracing window click on ‘Timing ‘check box.

To show Application Name in the main tracing window click on ‘Application Name’ check box.

To set up the ‘Log file’ tracing window click on ‘Log to file’ check box. It will allow you to type the name of the file directly into edit line box or use the ‘Browse’ button to open the standard ‘Select File’ dialog window.

You can close the Tracing Options window by clicking on the "OK" or "Cancel" buttons.

If "Cancel" button is clicked all current selections made in Tracing Options window will be lost.

If "OK" button is clicked tracing selections will be stored in the program configuration file and will be effective for the current and following sessions. Process selection information will be saved for current session only.

To get detail information on any trace row in any sheet window – double-click on it.

This will display Trace Detail Window:

You can keep this window open. Double clicking on another row will refresh it.

File operations of DBSPY 2.0 are straightforward. You can open New sheet window, Save or Log a trace and later Open it again in the application.

Multiple tracing sheets can be opened at the same time in DBSPY 2.0.

To open New trace sheet window from File menu, choose New or use the Frame Toolbar button:

Saving trace to a file is functionally similar to logging to a file. The only difference is that logging will do it one line at a time while saving takes all data from the active sheet window.

To save any Trace sheet window to a file:

It will open standard window Save as dialog where you can choose the directory and type the name of the file.

When saving to a file with an intent to open it in DBSPY in the future (example: to run a report) make sure that the format is "Text" (not "Text with headers"). For exporting to other applications the following formats are supported: HTML, EXCEL, CSV, DBASE.

Any valid ‘TXT’ file saved from available in DBSPY 2.0 application options such as ‘Logging to a file’, ‘Saving trace to a file ’ can be opened into a new tracing sheet window.

To open a previously saved file into a new sheet window from the File menu, choose Open or press Ctrl + O keys or use or use the Frame Toolbar button:

It will open standard window dialog where you can choose the directory and the file

Note:

This new window opened from a file becomes a valid trace window with all functions available in DBSPY 2.0 such as Report, Details and etc.

To copy any line from a Tracing window to the Clipboard

After tracing is completed you can generate the API performance report.

From the Reports menu, choose API Performance Report or use the Sheet Toolbar button (if visible).

API Performance Report window will be displayed.

The report will be generated for the current MDI sheet.

The generated report can be sorted by any column: Function, Count, Average Time, Minimum Time, and Maximum Time. In order to do it - click on the column header. Additional click will toggle the sort order for the column.

If you keep the Report window opened and switch to another trace sheet window you can simply get the API Performance Report for the window by pressing Refresh button.

The timing and count pie - charts on the report window can be maximized and later restored to original size.

Multiple tracing sheets can be opened at the same time during the session of DBSPY 2.0 .To see all open windows (sheets) choose one of the options in Window Menu:

DBSPY uses a configuration file - DBSPY.INI to store tracing options information for all database client libraries: DBLIB, CTLIB, SYBDB. Each library section has similar structure. Below is an example of a library section: