Powered by Zoomin Software. For more details please contactZoomin

DataDirect Connect for ADO.NET Data Provider Help

Storing Client Information

  • Last Updated: April 16, 2026
  • 2 minute read
    • ADO.NET
    • Documentation

Your application can store client information associated with a connection using the data provider connection string options listed in the following table. Refer to specific data provider sections for a description of each connection string option.

The following table shows the connection string options your application can use to store client information and where that client information is stored for each database.

Database Locations for Storing Client Information

Connection String Option Description Database Location
AccountingInfo Additional information that may be used for accounting or troubleshooting purposes, such as an accounting ID DB2 CURRENT CLIENT_ACCTNG register (DB2 for Linux/UNIX/Windows) or CLIENT ACCTNG register (DB2 for z/OS and DB2 for iSeries)
Oracle CLIENT_INFO value in the V$SESSION table
Microsoft SQL Server Local cache
Sybase Local cache
Application Name Name of the application that is currently using the connection DB2 CURRENT CLIENT_APPLNAME register (DB2 for Linux/UNIX/Windows) or CLIENT APPLNAME register (DB2 for z/OS and DB2 for iSeries). For DB2 V9.1 and higher for Linux/UNIX/Windows, this value is also stored in the APPL_NAME value in the SYSIBMADM.APPLICATIONS table.
Oracle CLIENT_IDENTIFIER attribute. In addition, this value is also stored in the PROGRAM value in the V$SESSION table.
Microsoft SQL Server Program_name value in the sysprocesses table
Sybase clientapplname and program_name value in sysprocesses table
Client Host Name Host name of the client on which the application using the connection is running DB2 CURRENT CLIENT_WRKSTNNAME register (DB2 for Linux/UNIX/Windows) or CLIENT WRKSTNNAME register (DB2 for z/OS and DB2 for iSeries)
Oracle MACHINE value in the V$SESSION table
Microsoft SQL Server Hostname value in the sysprocesses table
Sybase clienthostname and hostname value in sysprocesses table
Client User User ID for whom the application using the connection is performing work DB2 CURRENT CLIENT_USERID register (DB2 for Linux/UNIX/Windows) or CLIENT USERID register (DB2 for z/OS and DB2 for iSeries)
Oracle OSUSER value in the V$SESSION table
Microsoft SQL Server Local cache
Sybase clientname value in sysprocesses table
Program ID Product name and version of the driver on the client DB2 CLIENT_PRDID value. For DB2 V9.1 and higher for Linux/UNIX/Windows, the CLIENT_PRDID value is located in the SYSIBMADM.APPLICATIONS table.
Oracle PROCESS value in the V$SESSION table
Microsoft SQL Server The hostprocess value in the sysprocesses table
Sybase The hostprocess value in the sysprocesses table
TitleResults for “How to create a CRG?”Also Available inAlert