ASE ODBC Driver and OLE DB Provider Migration Technical - Sybase

More documents

Recommendations

Info

16 Application Name [applicationname/ApplicationName]: The name used by ASE to identify the client application. (Default = none) Client Host Name [clienthostname/ClientHostName]: Name of client host running the application using the ODBC Driver. This value must be populated if you want to use it. Client Host Process [clienthostprocess/ClientHostProcess]: This value is actually determined internally and automatically. It is the value of the process id belonging to the application using the ODBC Driver. This shows up in the TDS Login token and under the hostprocess column on the ASE sysprocesses table. Fetch Array Size [fetcharraysize/FetchArraySize]: Specifies the number of rows the driver retrieves when fetching results from the server. (Default = 25) Initialization String [initializationstring/InitializationString]: Session related SQL statements that can be sent to the ASE upon login time. Examples are set statements: set transaction isolation level 1 set textsize 64000 …. Language [language]: The language in which ASE returns error messages. (Default = empty, ASE uses English by default) Character Set [charset/CharSet]: Determines what character set is used for character translation between the client and ASE. User Specified: Enter the value to use if different from ASE. Example, if ASE is set to use iso_1 character set, and client wants to use cp850, then check this item and enter value “cp850”. This sets charset=cp850. Server Default: Upon login negotiation client uses character set specified by the ASE. This sets charset=ServerDefault. Client Default: When this is selected, charset=ClientDefault, and this uses the charset based on the operating system settings. In this case, another property is set, [codepagetype/CodePageType] and is set to either ANSI (ansi) or OEM (oem). Packet Size [packetsize/PacketSize]: When Server Packet Size is checked, this sets enableserverpacketsize/ EnableServerPacketSize to 1 [on by default], which enables ASE 15.0 or higher to choose an optimal packet size. The PacketSize property defaults to 512 bytes. When the property Restrict Maximum Packet Size [restrictmaximumpacketsize/ RestrictMaximumPacketSize] is set, ASE can only optimize to this value, unless ASE maximum packet size is less than this value, which is set in the dialog for Server Packet Size, and is actually set in the PacketSize property. Therefore, if the Server Packet Size dialog is set to 2048, then PacketSize=2048.
Transaction Tab Server Initiated Transactions [serverinitiatedtransactions/ServerInitiatedTransactions]: When SQL_ATTR_ AUTOCOMMIT is set to “1” Adaptive Server starts managing transactions as needed. The driver issues a “set chained on” command on the connection. Older ODBC Drivers do not use this feature and manage the job of starting transactions by calling begin tran. Set this property to “0” if you want to maintain the old behavior or require that your connection not use “chained” transaction mode. (Default = 1) Distribute Transactions: Used when ASE/DTM (Distribute Transaction Manager) is used on the ASE, which requires an ASE_DTM license. Tightly Coupled Transactions [tightlycoupledtransaction/ TightlyCoupledTransaction]: (Windows only) When using distributed transactions, if you are using two DSNs which connect to the same ASE server, set this to 1. See “Using Distributed Transactions” on page 41, in Chapter 3, “ASE Advanced Features.” (Default = 0) Distributed Transaction Protocol [distributedtransactionprotocol/ DistributedTransactionProtocol]: Allows the driver to use either an XA protocol or OleNative protocol when using distributed transactions. See “Using Distributed Transactions” on page 41, in Chapter 3, “ASE Advanced Features.” This is either of two values: XA or OLE. For windows clients only. (Default = XA) 17
Page 1 and 2: white papeR ASE ODBC Driver and OLE
Page 3 and 4: 1 intROductiOn The ODBC driver inte
Page 5 and 6: 5 suppORted pLatfORMs The ASE OLE D
Page 7 and 8: OLEDB The following OEM properties
Page 9 and 10: ODBC Connection Property Compatible
Page 11 and 12: This enables an application to refe
Page 13 and 14: Cursor Behavior Use Cursors [usecur
Page 15 and 16: When the primary server doesn’t r
Page 17: Kerberos This is used for ASE confi
Page 21 and 22: In the above diagram %SYBASE% = C:\
Page 23 and 24: The default install location is %SY

ASE ODBC Driver and OLE DB Provider Migration Technical - Sybase

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?