POrtability of ODBC and DBArtisan connection information
От | bdealhoy@sympatico.ca (Byrocat) |
---|---|
Тема | POrtability of ODBC and DBArtisan connection information |
Дата | |
Msg-id | b47d3acf.0403100829.70770bae@posting.google.com обсуждение исходный текст |
Список | pgsql-admin |
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!
В списке pgsql-admin по дате отправления: