How To Install and Configure the Lite
Edition ODBC Drivers for Microsoft SQL Server (Windows)
Pre-Installation Guide
You need to know a variety of information pertaining to your
target Microsoft SQL Server instance and database:
The Microsoft SQL Server version: Identify the
version of Microsoft SQL Server you are targeting.
Microsoft SQL Server instance name: Specify
the name of your SQL Server instance.
Microsoft SQL Server listen port: Provide the
listening port used by your SQL Server.
Microsoft SQL Server database name: Specify
the name of the target database you want to connect to.
Microsoft SQL Server database server hostname or IP
address: Provide the hostname or IP address of the server
where your SQL Server is located.
You need to know whether the client application is 32-bit or
64-bit. The Single-Tier (Lite Edition) ODBC Driver for Microsoft
SQL Server must match the bit format of the client
application.
Installation Guide
Download and double click on the downloaded .msi
file.
Your driver needs a license file to operate.
Click the Browse button to locate a commercial
or evaluation license that you have previously downloaded onto your
local hard drive.
Alternatively, click the Try & Buy button
to obtain a commercial or evaluation license.
64-Bit licenses are installed in
C:\Program Files\OpenLink Software\UDA\bin\.
32-Bit licenses are installed in
C:\Program Files (x86)\OpenLink
Software\UDA\bin\.
Proceed to configuring an ODBC Data Source Name (DSN) that
binds to your target SQL Server database.
Configuration Guide
Open the "ODBC Data Sources" Application.
64-bit drivers should be configured with the
64-bit Application.
32-bit drivers should be configured with the
32-bit Application.
Select the System DSN tab, then click Add.
Select the OpenLink "Lite" Driver for MySQL Data Sources from
the list of available drivers. Select the Unicode version of the
driver if and only if you are working with multi-byte character
sets, as unnecessary translations can significantly affect ODBC
performance.
Click Finish.
"The first dialog prompts for a Data Source Name and optional
description.
Click Next."
"The second dialog prompts for information that identifies the
Microsoft SQL Server DBMS and database. It also provides a checkbox
that allows you to check your basic connection parameters before
setting advanced and optional settings.
Server Name - Select the drop-down list box to
invoke the driver's Dynamic discovery of Microsoft SQL Server
instance on the network and choose the required instance, if
listed.
Connect now to verify that all settings are
correct - Will attempt to connect to the database once you
click Continue.
Login ID - A valid Microsoft SQL Server
username
Password - A valid Microsoft SQL Server
password
Use the Advanced button to manually configure a connection if
the Microsoft SQL Server instance could not be dynamically located,
as detailed below.
ServerType - An OpenLink proprietary parameter
that associates the connection with a particular TDS version.
Hostname - The hostname or IP address on which
Microsoft SQL Server listens
Port number - The TCP port on which Microsoft
SQL Server lists
Server Name - Microsoft SQL Server instance
name on the specified host. A Microsoft SQL Server instance can
also be specified by appending "\InstanceName" to the ServerName,
i.e., "ServerName\InstanceName"
Mirror Host - The name of the Failover Server
hosting the mirrored database if configured
Use strong encryption of data - Enable SSL
encryption of data between driver and database
Use Mars - Multiple Active Result Sets enables
the concurrent processing of multiple statements/queries and/or
result sets on a single connection
Verify Server Certificate - Verify the
Database Server SSL certificate against the one specified in the
"CA file" field
CA file - Specify the location of a Valid SSL
Certificate for use during the connection
Click Next.
"The third dialog takes a combination of database-specific and
optional parameters.
Database - The Microsoft SQL Server
database
Character set - The client application's
character set (8-bit only; the Unicode driver always returns UCS-2
on Windows).
Language - The language you want error
messages returned in; must be supported by the target server.
Packet Size - A value that determines the
number of bytes per network packet transferred from the database
server to the client. The correct setting of this attribute can
improve performance. When set to 0, the initial default, the driver
uses the default packet size as specified in the Microsoft SQL
Server configuration. When set to -1, the driver computes the
maximum allowable packet size on the first connect to the data
source and saves the value in the system information. When set to
x, an integer from 1 to 10, which indicates a multiple of 512 bytes
(for example, Packet Size of 6 means to set the packet size to 6 *
512 equal 3072 bytes). For you to take advantage of this connection
attribute, you must configure the System 10 server for a maximum
network packet size greater than or equal to the value you
specified for Packet Size.
Prepare Method - This option is specific to
the TDS-based driver for Sybase & Microsoft SQL Server SQL
Servers. It can take the values None, Partial, or Full
(connectoptions = -O [0, 1, 2] respectively). It is used to
determine whether stored procedures are created on the server for
calls to SQLPrepare.
No Quoted Identifiers - This option indicates
that the underlying driver does not support quoted identifiers,
which is required for Jet engine-based products like MS
Access.
Use ANSI nulls, padding and warnings - This
option affects TDS agent & Lite Driver connections to Microsoft
SQL Server databases. Sybase connectivity is not affected.
Map Serializable to Snapshot isolation level -
Enable Snapshot transaction isolation level in the driver. Snapshot
Isolation is a new transaction isolation level available in
Microsoft SQL Server 2005.
Click Next.
"The fourth dialog enables you to set optional ODBC connection
parameters.
Read-only connection â Specifies whether the
connection is "Read-only." Must be unchecked to INSERT, UPDATE, or
DELETE records, and to run some Stored Procedures including some
built-in functions.
Defer fetching of long data â Defers
fetching of LONG (BINARY, BLOB, etc.) fields in wildcard queries.
This provides significant performance increases when fields in
query do not include LONG data fields.
Disable interactive login â Suppresses the
ODBC "Username" and "Password" login dialog boxes when interacting
with your ODBC DSN from within an ODBC compliant application.
Row Buffer Size â This attribute specifies
the number of records to be delivered from the driver to the client
application in a single batch. Values can range from 1 to 999.
Max Rows Override â Allows you to set a
limit for the maximum number of rows to be returned from a query.
The default value of 0 means no limit.
Initial SQL â Lets you specify a file
containing SQL statements that will be run automatically against
the database upon connection.
Dynamic Cursor Sensitivity â Enables or
disables the row version cache used with dynamic cursors. When
dynamic cursor sensitivity is set high, the Cursor Library
calculates checksums for each row in the current rowset and
compares these with the checksums (if any) already stored in the
row version cache for the same rows when fetched previously. If the
checksums differ for a row, the row has been updated since it was
last fetched and the row status flag is set to SQL_ROW_UPDATED. The
row version cache is then updated with the latest checksums for the
rowset. From the user's point of view, the only visible difference
between the two sensitivity settings is that a row status flag can
never be set to SQL_ROW_UPDATED when the cursor sensitivity is low.
(The row status is instead displayed as SQL_ROW_SUCCESS.) In all
other respects, performance aside, the two settings are the same.
Deleted rows don't appear in the rowset. Updates to the row since
the row was last fetched are reflected in the row data, and
inserted rows appear in the rowset, if their keys fall within the
span of the rowset. If your application does not need to detect the
row status SQL_ROW_UPDATED, you should leave the High Cursor
Sensitivity checkbox unchecked, as performance is improved. The
calculation and comparison of checksums for each row fetched carry
an overhead. If this option is enabled, the table oplrvc must have
been created beforehand using the appropriate script for the target
database.
Enable logging to the log file â Check the
checkbox and use the associated textbox to provide the full path to
a file in which to log diagnostic information.
Click Next.
"The fifth dialog enables you to set additional parameters to
enhance compatibility with applications.
Enable Microsoft Jet engine options â
Facilitates the translation of certain data types for the Microsoft
Jet Engine. If you notice that money and other data types are
mishandled with Microsoft or other applications, test with Jet fix
enabled.
Disable Autocommit â Changes the commit
behavior of the OpenLink driver. The default mode is AutoCommit
(box unchecked).
Disable rowset size limit â Disables a
limitation enforced by the cursor library. This limitation is
enforced by default. It prevents the driver from claiming all
available memory when a resultset (typically generated by an
accidental query) is very large. The limit is not normally
reached.
Multiple Active Statements Emulation â
Enables the use of Multiple Active statements in an ODBC
application even if the underlying database does not allow this, by
emulation within the driver.
SQL_DBMS Name â Manually overrides the
SQLGetInfo(SQL_DBMS_NAME) response returned by the driver. This is
required for products like Microsoft InfoPath for which the value
should be "SQL Server".
Click Next.
The final dialog enables you to test your Data Source. Click
the Test Data Source button.
This document is empty and basically useless. It is generated by a web service that can make some statements in HTML+Microdata format.
This time the service made zero such statements, sorry.