17.10 - Client-Server UDF Code Specification - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - SQL Data Definition Language Detailed Topics

Advanced SQL Engine
Teradata Database
Release Number
July 2021
English (United States)
Last Update

You must specify whether the UDF code for include files, object files, and source files is located on the client system or on the server. To do this, you specify C for client or S for server.

UDF code for library and package files is always located on the server, but you still must specify the S location code for any library or package file paths you specify.

The character used to separate entities in the path specification is platform-specific when the file is stored on a client system, but not when the file is on the server.

The following table provides more information about writing the client and server location specifications for include, object, or source files:

IF you specify this location code … THEN you …
C must format the specification in the form required by the client application, for example, BTEQ.

Refer to the appropriate client documentation for information about the required form of presentation.

S can use either the SOLIDUS character (/) or the REVERSE SOLIDUS character (\) as the separator in the path specification for all platform operating systems.