 | SQL Engine Reference (v9 SP2 (9.5) revision 1) |  |
|
A connection string used to connect to a DSN may include any number of driver-defined keywords. Using these keywords, the driver has enough information to connect to the data source. The driver (for example, the Pervasive ODBC Engine Interface or Pervasive ODBC Client Interface) defines which keywords are required to connect to the data source.
Connection strings serve the same purpose in Pervasive PSQL v9 Service Pack 2 as they did in previous versions. They are used to identify which data source to connect to. The difference now lies in the driver-defined keywords listed in the connection string. Pervasive.SQL 7 used a different set of keywords to identify a data source.
Listed below are the keywords used in Pervasive PSQL v9 Service Pack 2 connection strings.
|
DSN
|
Name of the data source as returned by SQLDataSources or the data sources dialog box of SQLDriverConnect.
|
|
DRIVER
|
The description of the driver as returned by SQLDrivers function. For a Client DSN, it is "Pervasive ODBC Client Interface".
|
|
ServerName
|
The address of the server or host name and the port number where the data resides. See also Changing the Default Communication Ports in Getting Started With Pervasive PSQL (Server Edition).
|
|
ServerDSN
|
The name of an Engine data source referenced by this DSN.
|
|
TransportHint
|
Specifies the transport protocols to check for the ServerName. The list of transport protocols is specified in the order in which they should be searched.
|
|
PWD
|
The password corresponding to the user ID.
|
|
ArrayFetchOn
|
Enable array fetching. Array fetching is used to improve performance of data fetching between the client and the server. The default setting is to enable array fetching.
|
|
ArrayBufferSize
|
Size of the array buffer. Values between 1 and 64KB are acceptable. The default setting is 8KB.
|
|
UID
|
A user login ID.
|
|
Chapter contents
Prev topic: Pervasive Relational Interface Limits
|