Multi Instance job log message
Posted: Tue Mar 19, 2013 8:56 am
There are 20 reference table (Sql server tables) that are to be loaded to 20 different datasets.
The table structures are different and all the tables are in the same database.
A single table may be required to be executed at the same time in different sequence jobs.
A table will be executed only once in a sequence.
Solution:
I have created one job to read from the table ( ODBC_Connector) to load into dataset, with no other stages in between . the column definition is not defined in ODBC stage and dataset. Turned on the multi instance property along with RCP.
For each run pass the table name and dataset name through parameter in sequence each time for 20 refernce tables.
Is this a workable solution?
Log message:
There is a info messge in log as below for each column in the table.
ODBC_EmpCodes: External schema field, name: SrcSysCode, type: INT16 was not found in the design schema
External schema field, name: SrcCode1, type: STRING was not found in the design schema
Are there any effects of this kind of message. Why is this appearing in the log? can anyone explain this ?
The table structures are different and all the tables are in the same database.
A single table may be required to be executed at the same time in different sequence jobs.
A table will be executed only once in a sequence.
Solution:
I have created one job to read from the table ( ODBC_Connector) to load into dataset, with no other stages in between . the column definition is not defined in ODBC stage and dataset. Turned on the multi instance property along with RCP.
For each run pass the table name and dataset name through parameter in sequence each time for 20 refernce tables.
Is this a workable solution?
Log message:
There is a info messge in log as below for each column in the table.
ODBC_EmpCodes: External schema field, name: SrcSysCode, type: INT16 was not found in the design schema
External schema field, name: SrcCode1, type: STRING was not found in the design schema
Are there any effects of this kind of message. Why is this appearing in the log? can anyone explain this ?