15.00 - UDF Default Location Paths  - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

Teradata Database
Release Number
Content Type
Programming Reference
Publication ID
English (United States)

UDF Default Location Paths 

User‑defined functions expect information to be in certain default locations when they are created or performed.

The following list catalogs the default path locations used by UDFs for the following purposes:

  • Store UDF source files
  • Compile UDF source files
  • Store .dll or .so files
  • Store shared memory files
  • The following table documents the default directory paths for these resources and activities.



    Directory Path


    Header file


    The header file sqltypes_td.h must be specified with an include directive in the UDF source.

    You can copy this file if you code or compile the UDF outside of the database.

    Source directory path


    The default directory to search for source files.

    If the source or object file is on the server in this directory, then you can specify the relative path from this directory for any server components specified in the external name string.

    This applies to all the following file types:

  • Include
  • Object
  • Package
  • Source
  • Compiler path


    The default directory to search for the C/C++ compiler.

    Linker path


    The default directory to search for the C/C++ linker.

    Compiler temporary path


    the temporary directory where UDFs are compiled

    Any files needed for the compilation process are moved here. This includes source files from the server or client as well as object and header files, if needed.

    Temporary compilation directories only exist during the duration of a compilation.

    UDF library path


    the directory where dynamically linked libraries are stored.

    UDF server memory path


    the directory where shared memory files used for the execution of protected mode UDFs are stored.