ODBC Notes

Intro

http://msdn2.microsoft.com/en-us/library/aa936940(SQL.80).aspx

Warning While the DB-Library API is still supported in Microsoft SQL Server 2000, no future versions of SQL Server will include the files needed to do programming work on applications that use this API. Connections from existing applications written using DB-Library will still be supported in the next version of SQL Server, but this support will also be dropped in a future release. When writing new applications, avoid using DB-Library. When modifying existing applications, you are strongly encouraged to remove dependencies on DB-Library. Instead of DB-Library, you can use Microsoft ActiveX® Data Objects (ADO), OLE DB, or ODBC to access data in SQL Server.

Loadrunner appears to be recording MS SQL Server database sessions by hooking into the DB-Library (they call it DBLIB). Therefore, the recording feature in Loadrunner does not work with newer versions of SQL Server clients (e.g. SQL Server 2005 and Microsoft SQL Server Management Studio Express (SSMSE)).

ODBC Recording in Loadrunner.

Setup an ODBC source.

Also see MS SqlServer Notes as that page illustrates the configuration process.

Run odbcad32.exe

 Name the source - say, mytestdb

Configure Squirrel SQL using the JDBC-ODBC Bridge Driver.

 DSN == jdbc:odbc:mytestdb

Test the connection.

Now, create a Loadrunner ODBC VU script.

Record a Win32 application and execute Squirrel SQL.

Make sure that you run the right pieces to record the ODBC conversation between the ODBC manager (odbcad32.exe) and Squirrel SQL.

This should easily translate over to unixODBC or iODBC in UNIX (and Python) land which I think you already mentioned.

http://www.egenix.com/products/python/mxODBC/

Recording JTDS does not work in Loadrunner because Loadrunner is still using the DB-Library hook. JTDS uses the native freetds library and JDBC.

However, in the future, I would guess that Loadrunner will eventually have a JDBC recorder.