# tDB2SP Offers a convenient way to call the database stored procedures. ## tDB2SP Standard properties These properties are used to configure tDB2SP running in the Standard Job framework. The Standard tDB2SP component belongs to the Databases family. The component in this framework is available in all Talend products. Information noteNote: This component is a specific version of a dynamic database connector. The properties related to database settings vary depending on your database type selection. For more information about dynamic database connectors, see [DB Generic components](https://help.qlik.com/talend/r/en-US/8.0/components/db-generic/db-generic-component). ## Basic settings | Properties | Description | | --- | --- | | Database | Select the desired database type from the list and click
Apply. | | Use an existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined.

Information noteNote: When a Job contains the parent Job and the child Job, do the following if you
want to share an existing connection between the parent Job and the child Job (for example,
to share the connection created by the parent Job with the child Job).

In the parent level, register the database connection to be shared in the Basic settings view of the connection component which creates that very database connection.
In the child level, use a dedicated connection component to read that registered database connection.

For an example about how to share a database connection across Job levels,
see [Sharing a database connection](https://help.qlik.com/talend/r/en-US/7.3/studio-user-guide/sharing-database-connection). | | Property type |

Either Built-in or Repository .
Built-in: No property data stored centrally.
Repository: Select the repository file in which the properties are stored. The fields that follow are completed automatically using the data retrieved.

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.
Built-In: You create and store the schema locally for this component only.
Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
- View schema: choose this option to view the schema only.
- Change to built-in property: choose this option to change the schema to Built-in for local changes.
- Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.
  
  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

| | SP Name | Type in the exact name of the Stored Procedure | | Is Function / Return result
in | Check this box, if a value only is to be returned.

Select on the list the schema column, the value to be returned is
based on. | | Parameters | Click the ![Add](https://help.qlik.com/talend/en-US/components/8.0/Resources/images/add.svg) button, and select the various Schema
Columns that will be required by the procedures. Note that the
SP schema can hold more columns than there are parameters used in the
procedure.

Select the Type of parameter:

IN: input parameter.
OUT: output parameter/return value.
IN OUT: input parameter is to be returned as value, likely after modification through the procedure (function).
RECORDSET: input parameter is to be returned as a set of values, rather than single value.

Select a database type from the DB
Type list to map the source database type to the target database
type:

AUTO-MAPPING: map the source database type to the target database type automatically.
DATE: string containing the date in the following format YYMMDD
TIMESTAMP: string containing the date and time in the following format YYYY-MM-DD-HH.MI.SS.999999.
TIME: string containing the time in the following format HHMISS999.

Information noteNote:

Check [Inserting data in mother/daughter tables](https://help.qlik.com/talend/en-US/components/8.0/mysql/tmysqlconnection-tmysqlrollback-tfileinputdelimited-inserting-data-in-mother-daughter-tables-standard-component-the) if you want to analyze a set
of records from a database table or DB query and return single
records. | | Specify a data source alias | Select this checkbox and specify the alias of a data source created on the *Talend Runtime* side to use the shared connection pool defined in the data source configuration. This
option works only when you deploy and run your Job in *Talend Runtime*.

This checkbox is not available when the Use an existing
connection checkbox is selected. | | Data source alias | Enter the alias of the data source created on the *Talend Runtime* side.

This field is available only when the Specify a data
source alias checkbox is selected. | ## Advanced settings | Properties | Description | | --- | --- | | Additional JDBC parameters | Specify additional connection properties for the DB connection you
are creating.

Information noteNote:

You can set the encoding parameters through this field. | | tStat
Catcher
Statistics | Select this check box to collect log data at the component
level. | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component is used as intermediary component. It can be used
as start component but only input parameters are thus allowed. | | Dynamic settings | Click the [+] button to add a row in the table
and fill the Code field with a context
variable to choose your database connection dynamically from multiple
connections planned in your Job. This feature is useful when you need to
access database tables having the same data structure but in different
databases, especially when you are working in an environment where you
cannot change your Job settings, for example, when your Job has to be
deployed and executed independent of Talend Studio.

The Dynamic settings table is
available only when the Use an existing
connection check box is selected in the Basic settings view. Once a dynamic parameter is
defined, the Component List box in the
Basic settings view becomes unusable.

For examples on using dynamic parameters, see [Reading data from databases through
context-based dynamic connections](https://help.qlik.com/talend/r/en-US/8.0/components/defining-context-groups/reading-data-from-databases-through-context-based-dynamic-connections) and [Reading data from different MySQL databases
using dynamically loaded connection parameters](https://help.qlik.com/talend/r/en-US/8.0/components/context/reading-data-from-different-mysql-databases-using-dynamically-loaded-connection-parameters). For more information on
Dynamic settings and context variables, see
[Dynamic schema](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/dynamic-schema) and [Creating a context group and define context
variables in it](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-context-group-and-define-context-variables-in-it). |