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...
BruceHi Bruce,
Just wanted to ask if you have already installed the ODBC drivers for
all the other databases i.e. Sybase, SQL Server, Informix and Oracle?
Regards,
Ashok Rautela
"Byrocat" <strikemaster2000@.yahoo.ca> wrote in message news:<CM50c.68204$ee3.635958@.news20.
bellglobal.com>...
> 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 an
y
> impact? (eg, just DB2)
> Thanks in advance...
> Bruce|||arautela@.openlinksw.co.uk (Ashok Rautela) wrote in message news:<f5f56ae7.0403020312.44da8d
0a@.posting.google.com>...
> Hi Bruce,
> Just wanted to ask if you have already installed the ODBC drivers for
> all the other databases i.e. Sybase, SQL Server, Informix and Oracle?
> Regards,
> Ashok Rautela
>
I definitely have DB2, Sybase and SQLServer ODBC drivers installed.
I don't think that that is the problem. I've played with the list
entries (having created and recreated the list via the Registry), and
can get the cut-off point to change locations.
Defintiely points to the buffer being hard-coded.
Did have an interesting suggestion... Could the MS ODBC Administrator
make use of a registry entry to determine the maximum size of its
buffer and can this be changed?|||I remember a posting from someone at Microsoft that the
limitation is the combined length of the DSNs cannot exceed
4096 characters. So if you have DSN names that are all 409
characters long, you can only have 10 of those that will
display in the ODBC Data Source Administrator. If you create
more DSNs after this, they won't show up in the
Administrator applet but will be written to the registry and
will be available for use by applications.
-Sue
On 2 Mar 2004 09:07:38 -0800, bdealhoy@.sympatico.ca
(Byrocat) wrote:
>I definitely have DB2, Sybase and SQLServer ODBC drivers installed.
>I don't think that that is the problem. I've played with the list
>entries (having created and recreated the list via the Registry), and
>can get the cut-off point to change locations.
>Defintiely points to the buffer being hard-coded.
>Did have an interesting suggestion... Could the MS ODBC Administrator
>make use of a registry entry to determine the maximum size of its
>buffer and can this be changed?
