If you are working on an SVN or Git managed project while the Manual lock option is selected in Talend Administration Center, be sure to lock manually your connection in the Repository tree view before retrieving or updating table schemas for it. Otherwise the connection is read-only and the Finish button of the wizard is not operable. For more information about locking and unlocking a project item and on different lock types, see Working collaboratively on project items.
Right-click the SAS connection you created and then select Retrieve Schema from the contextual menu.
A new wizard opens up where you can filter and show different objects (tables, views) in your database connection, select tables of interest, and define table schemas.
Filter databases objects according to your need, select one or more tables of interest, and modify the table schemas if needed. For details, see Retrieving table schemas.
Make sure the data type in the Type column is correctly defined.
For more information regarding Java data types, including date pattern, see Java API Specification.
Below are the commonly used Talend data types:
Object: a generic Talend data type that allows processing data without regard to its content, for example, a data file not otherwise supported can be processed with a tFileInputRaw component by specifying that it has a data type of Object.
List: a space-separated list of primitive type elements in an XML Schema definition, defined using the xsd:list element.
Dynamic: a data type that can be set for a single column at the end of a schema to allow processing fields as VARCHAR(100) columns named either as 'Column<X>' or, if the input includes a header, from the column names appearing in the header. For more information, see Dynamic schema.
Document: a data type that allows processing an entire XML document without regarding to its content.
When done, you can drag and drop any table schema of the SAS connection from the Repository tree view onto the design workspace as a new component or onto an existing component to reuse the metadata. For more information, see How to use centralized metadata in a Job and How to set a repository schema in a Job.