Database type trees

Edit online

Use the Database Interface Designer or mtsmaker to generate a type tree to be used in a map. You can also define your own type tree using the Type Designer. However, for the database adapters to correctly process your database data, your type tree must conform to the format described in this topic. For information about using mtsmaker to generate type trees, see the Resource Adapters documentation.

Although you can manually create a type tree for a table or a query using the Type Designer, it is not recommended.

The following examples represent type trees generated by the Database Interface Designer from two queries (one SELECT and one calls a stored procedure), a table, a stored procedure, and a message queue.

As shown in these examples, the type trees generated from tables, views, queries, and stored procedures are very similar, while the type tree generated for message queues differs slightly.

In these example type trees:

  • The type tree named ActvProj.mtt was created for a query that referenced a Microsoft Access table.
  • The type tree named Stores.mtt was created for a table in a Microsoft SQL Server database.
  • Two type trees were created for stored procedures in an Oracle database.
    • The PymtInfo.mtt type tree was generated for a query called GetPaymentInfo that calls an Oracle stored procedure to be used as a map data source.
    • The ApplyPmt.mtt type tree was generated for the SCOTT.APPLY_PAYMENT stored procedure to be used as a map output.
  • The type tree named Paulmsg.mtt was generated from a message queue on the PAUL_MSG_QUEUE.