Re: POrtability of ODBC and DBArtisan connection information

From: "Campano, Troy" <Troy(dot)Campano(at)LibertyMutual(dot)com>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: POrtability of ODBC and DBArtisan connection information
Date: 2004-03-15 21:42:56
Message-ID: 82C3FD729CFA504CA44E7D32BDED411F0887F7E2@lm-exmsg-07.lm.lmig.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Isn't this a DB2 question and not a PostgreSQL question?
How does this relate to PostgreSQL? I'm lost.

Thanks!

-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Byrocat
Sent: Wednesday, March 10, 2004 11:29 AM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] POrtability of ODBC and DBArtisan connection
information

Here's the situation:

We're doing user administration on a pile (250+) DB2 databases, and
are using ODBC to provde the connection to these database (plus a
whole pile of ones from other database providers). The desktop is
Windows 2000 and we're running the client ODBC software for DB/2.

Right now, I've got two BIG problems.

The first is that the ODBC connections have to be created by hand. I'm
using MS ODBC Administrator to do this, and have already created an
alias list that's completely independent of the name of the database).
Yes, we have mulitple databases defined on multiple instances on
multiple servers, with duplicate database names galore. So, aliases
are going from "AAAAAAAA" to whatever I hit when I complete the list
of ALL DB2 databases.

The second is that we're using Embarcadero DBArtisan as the
administrative tool. This requires that the database connection be
registered within the application for it to be usable.

There is the requirement that the desktop environment (connection
information and DBArtisan registry list) be retained in a version
control environment, PLUS be loaded unto other administration
desktops.

So, I'm looking for two solutions:
How to automate the process of creating an ODBC connection and
registering it in DBArtisan.
How to export the data for the ODBC connection (Windows Registry is
easy, but where is the alias/server/port information retained)as well
as the DBArtisan registrations, and how to import them.

Any help, pointers, or better yet TOOLS, are greatly appreciated.

Better to reply directly if at all possible.

Thanks in advance!

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
message can get through to the mailing list cleanly

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2004-03-15 22:07:09 Re: nodeRead: did not find '}' at end of plan node
Previous Message Martin Sarsale 2004-03-15 21:07:03 nodeRead: did not find '}' at end of plan node