Moving Jobs Across Servers, need to export Table Defs?

[kadf88]

Is it neccessary to export/import Table Definitions when I'm moving a job from one server to another? Assuming the environment (hardware, OS) ar the same?

We experimented with this and seems like you do indeed need to import/export the table defs but it doesn't make sense because you can move jobs across projects (same server) without moving the table defs. And doesn't DS store the table defs internally to the job once you compile?

Thanks, any help is appreciated.

[dwandbi]

I don't think to export data definitions when you are exporting/importing a server job from one server to other. Say from dev to prod box.

check DS Manager guide once.

thanks,
Tom

[trobinson]

It is not necessary to move a table def with a job when exporting/importing. What experiment were you doing that indicated otherwise?

[kadf88]

well, the experiment was just that, moving a job across servers. It wasn't able to compile when we just moved the job without table defs. But when we included the table defs, it compiled.

[dwandbi]

If the servers(Dev and Prod) are located on once box then no need to ex/im table definitions along with server job executables.

thanks,
Tom

[gateleys]

Hi Tom,

I don't think to export data definitions when you are exporting/importing a server job from one server to other. Say from dev to prod box.

Your first response says that if Dev and Prod belong to two different boxes, then there is no need to export metadata.

If the servers(Dev and Prod) are located on once box then no need to ex/im table definitions

However, your second response says that if Dev and Prod are in the same box, then it does not necessitate metadata export.

So, if I were to combine both your posts, it means irrespective of the location of the the projects, there is no need to export metadata. Am I correct?

Thanks,
gateleys

[kadf88]

what if they are located on different boxes?

cause i think they are

[kcbland]

Table Definitions stored in Manager are not necessary for executing or importing a job design. Proper metadata management is a different topic. You should consider keeping all design information together no matter which environment. A table definition is copied into a job design with a silent link between each column and the definition loaded. You can delete a table definition from Manager without affecting the job design. You can also type into a job design metadata that has no stored definition and everything will work.

[ray.wurlod]

If you use Usage Analysis in Manager or MetaStage, and expect it to work properly in the new environment, then you must migrate the table definitions.

[sb_akarmarkar]

Hi,

To keep track of table defination or table use by Jobs, we need to import/export table defination.

Example: Suppose our table design change in backend database then it is diffcult to track ETL which are using this table need to modify for change.
If we have table defination we can esaily get ETL information from manger.

Best practice always import/export all metadata.

Thanks,
--Anupam
akarmarkar@smart-bridge.co.in

[kumar_s]

To facilitate the porcess of collecting the table defenitions to a centelized repository, MetaBrokers can be used.