Import Table Definitions

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

Post Reply
poorna_76
Charter Member
Charter Member
Posts: 190
Joined: Thu Jul 08, 2004 10:42 am

Import Table Definitions

Post by poorna_76 »

We are trying to import TableDefintions from the
Manager -ImportTableDefinitions -ODBC TableDefinitions.

If we are trying to import the TableDefinitions from the default Database defined for the ODBC connection(DSN), it works fine.
If we try to import the TableDefinitions from the different Database using the same ODBC connection(DSN), it does not work.

We tried to import using Plug-in MetaDefinitions, but the defintions are not matching with definitions on SQL Server.

Is there a way we can define a generic ODBC connection for different Databases on the same server,
so that we can import table definitions for all the tables in all databases on that Server, using the same DSN?

Thanks in Advance
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Re: Import Table Definitions

Post by chulett »

poorna_76 wrote:Is there a way we can define a generic ODBC connection for different Databases on the same server, so that we can import table definitions for all the tables in all databases on that Server, using the same DSN?
No that I'm aware of.
-craig

"You can never have too many knives" -- Logan Nine Fingers
I_Server_Whale
Premium Member
Premium Member
Posts: 1255
Joined: Wed Feb 02, 2005 11:54 am
Location: United States of America

Post by I_Server_Whale »


Is there a way we can define a generic ODBC connection for different Databases on the same server,
so that we can import table definitions for all the tables in all databases on that Server, using the same DSN?
Hi Poorna,

I don't think that is ever possible unless all databases have same drivers. The reason we create different ODBC connections for different databases is because of the unique drivers for each database.

Thanks,
Naveen.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Talk to IBM about the Information Integrator product.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
poorna_76
Charter Member
Charter Member
Posts: 190
Joined: Thu Jul 08, 2004 10:42 am

Post by poorna_76 »

naveendronavalli wrote:

Is there a way we can define a generic ODBC connection for different Databases on the same server,
so that we can import table definitions for all the tables in all databases on that Server, using the same DSN?
Hi Poorna,

I don't think that is ever possible unless all databases have same drivers. The reason we create different ODBC connections for different databases is because of the unique drivers for each database.

Thanks,
Naveen.
Hi All,

Thanks for all the suggestions.

I mean different databases(DB1,DB2...) on
one RDBMS ( SQL Server in my case).

I don't mean different Databases as Oracle,SQL Server,DB2 etc.


Currently we have ODBC connection(DSN) defined at Server with no default database selected.


All my DataStage jobs works fine, even though they read data from different databases(DB1,DB2..) using same ODBC connection, if we prefix the table name with Database name.

Only issue we are facing is while importing the TableDefinitions.

Thanks in Advance.
Post Reply