When I import an ODBC table definition, then load the column definitions into an ODBC stage, I have a problem. The "derivation" for each column includes the database name, table owner, and table name.
e.g.
Instead of having "customer_name" in the derivation, it has "dev_db.dbo.customer_tbl.customer_name".
This causes problems when I promote this job to another environment, because "dev_db" is now named "prod_db" (for example). So during my development, I have to manually edit the derivation for every database column and remove the database name so that it will work in all environments.
Is there a way to prevent this behavior?
Importing ODBC table defs
Moderators: chulett, rschirm, roy
I'm assuming this will work as it does for the OCI stages...
Don't "Load" the metadata from inside the stage. Instead, make sure Table Definitions are showing in your Repository Browser and then drag the metadata to the link on your ODBC Stage. Doing it this way will leave the Derivation column alone.
Don't "Load" the metadata from inside the stage. Instead, make sure Table Definitions are showing in your Repository Browser and then drag the metadata to the link on your ODBC Stage. Doing it this way will leave the Derivation column alone.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
The way that I have gotten around this problem is after I import the table definitions, I edit the table definition by removing the database name and owner from the Table/File Name field. Then when I import the columns into an ODBC stage the derivation field is just the TableName.ColumnName. It is still a little extra work but it is easier than changing every derivation for each column.
