Neoview ADO.NET Provider Manual (R2.5)

3 ADO.NET for Neoview
The Neoview ADO.NET provider conforms where applicable to the Microsoft ADO.NET
specification. The Neoview ADO.NET provider differs from the standard in some ways, and has
these Neoview-specific implementations for connection strings and schemas:
“Neoview ADO.NET Connection String” (page 15)
“Neoview Schema Collections for ADO.NET (page 16)
“Restrictions and Extensions of ADO.NET Methods and Properties for the Neoview Platform”
(page 19)
Neoview ADO.NET Connection String
Neoview ADO.NET uses standard syntax for parsing connection strings.
The format of a connection string is a series of keyword and value pairs connected with equals
signs and separated by semicolons:
Server=arc0101.cup.hp.com:18650;catalog=neo;password=myneoviewpw;user=JSmith
Keywords in the connection string are not case-sensitive.
Connection String Properties
Three properties are required to be set for any connection:
Server
User
Password
The rest of the connection string properties are optional.
These are the properties you can set for a Neoview ADO.NET connection string:
Table 3-1 Connection String Properties
DescriptionDefaultName
Host name of the Neoview Server, in the form host_name:port.
Example: arc0101.cup.hp.com:18650
N.A.
Server
Required
Server-side data source name
Example: TDM_Default_DataSource
N.A.
DataSource
Default catalog
Example: Neo
N.A.
Catalog
Default schema
Example: my_schema
N.A.
Schema
User name
Example: JSmith
N.A.
User
Required
Password
Example: mypasswd
N.A.
Password
Required
LDAP Secondary Role
Example: ROLE.MGR
N.A.
RoleName
Number of times to retry connecting if attempts fail3
RetryCount
Time in milliseconds to wait between retries5000
RetryTime
Indicates whether TCP KeepAlive should be enabled on socketsTrue
TcpKeepAlive
Neoview ADO.NET Connection String 15