1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
5
>ODBC-combined configuration</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
TITLE="FreeTDS User Guide"
11
HREF="index.htm"><LINK
13
TITLE="Preparing ODBC"
14
HREF="prepodbc.htm"><LINK
16
TITLE="ODBC-only configuration"
17
HREF="odbcinionly.htm"><LINK
19
TITLE="Troubleshooting ODBC connections"
20
HREF="odbcdiagnose.htm"><LINK
23
HREF="userguide.css"></HEAD
34
SUMMARY="Header navigation table"
46
> User Guide: A Guide to Installing, Configuring, and Running <SPAN
57
HREF="odbcinionly.htm"
65
>Chapter 4. Preparing ODBC</TD
71
HREF="odbcdiagnose.htm"
86
>ODBC-combined configuration</A
89
>Like the DSN-less configuration, ODBC-combined keeps server properties in <TT
92
>. The difference is that your applications can refer to the server by its DSN. To make that possible, the DSN entry in <TT
95
> refers to the dataserver entry in <TT
103
NAME="E.G.SAMPLEODBCCOMBO"
107
>Example 4-5. Sample ODBC-combined <TT
113
CLASS="PROGRAMLISTING"
114
>[ODBC Data Sources]<A
122
JDBCdsn = Sybase JDBC Server
125
Driver = /usr/local/freetds/lib/libtdsodbc.so
126
Description = Sybase JDBC Server
139
Driver = /usr/local/freetds/lib/libtdsodbc.so</PRE
145
NAME="E.G.SAMPLECOMBOFILE"
149
>Example 4-6. Sample ODBC-combined <TT
155
CLASS="PROGRAMLISTING"
160
host = jdbc.sybase.com
162
tds version = 5.0</PRE
167
>With this arrangement, an application can connect to the server in two ways, via its DSN (<TT
170
>), or its dataserver name (<TT
190
HREF="odbcombo.htm#AEN1750"
201
>Several DSNs might be listed here. In this example, we have only one, <SPAN
204
>. It matches the <TT
207
> entry later in the file. </P
217
HREF="odbcombo.htm#AEN1754"
243
SUMMARY="Footer navigation table"
254
HREF="odbcinionly.htm"
272
HREF="odbcdiagnose.htm"
282
>ODBC-only configuration</TD
296
>Troubleshooting ODBC connections</TD
b'\\ No newline at end of file'