DSN's do not display in ODBC Data Source Administrator
From: Byrocat (strikemaster2000_at_yahoo.ca)
Date: 02/28/04
- Next message: Igor Shekalev: "Re: ODBC sniffing..."
- Previous message: BusyByte: "You can not use an OLE DB provideer for ODBC driver"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 28 Feb 2004 14:00:41 -0500
I'm currently having to create a raft of DB2 connections in a
reasonable hurry. In addition, this list has to be propogated to three
other workstations (ultimate goal is to have DBArtisan access the
servers, instances and databases in an identical manner without having
to spend days doing this manually.)
I've figured out that the registry keys
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
and
HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources
allow me to specify the System DSN's so that they can be picked up by
the ODBC Data Source Administration application.
Unfortuantely, I think that there's a hidden limit in how much data
the tool can handle. Somewhere around 155 of the 219 DSN's, one row
gets chopped.
Instead of a line that reads
server.instance.database IBM DB2 ODBC DRIVER
I get variants such as the latest:
server.insta <rest of line is blank>
Looks like a classic buffer reaches max-size, burp and do nothing but
continue running.
BTW, this is only the tip of the iceberg, not only are there going to
be 200+ DB2 databases, but we're also looking at Sybase, MS SQLServer,
Informix, and Oracle, plus a few other antique clangers and
boat-anchors.
A follow-up question, would shortening the name of the ODBC server have any
impact? (eg, just DB2)
Thanks in advance...
Bruce
- Next message: Igor Shekalev: "Re: ODBC sniffing..."
- Previous message: BusyByte: "You can not use an OLE DB provideer for ODBC driver"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|