Table of contents
TOC
Collapse the table of content
Expand the table of content

Data Definition Language (DDL) Statements (U-SQL)

Michael Rys|Last Updated: 5/15/2018
|
4 Contributors

While one of U-SQL’s strength is to operate on unstructured data stored in files, it can also provide structured views over the unstructured data, manage structured data in tables and provides a general metadata catalog system to organize your structured data and custom code, secure it and make it discoverable.

Each meta data object is given a name and the objects are arranged in the following object hierarchy:

U-SQL Metadata Object Model

U-SQL metadata objects are name-scoped to their containers (e.g., views and tables are scoped to database schemas) which provide a single namespace for all object types within a container. Thus names cannot be shared across different object types in the same container (e.g., a view and table in the same schema cannot have the same name). The metadata objects are addressed with their U-SQL object identifier (follow the link for more information on the form of U-SQL object identifiers and how they are being resolved).

Objects that are included from the C# context, such as the names of functions, classes, methods provided by the assemblies, do not require metadata object names but instead are being references using their C# names after the assemblies are being referenced by their metadata object names in the scripts.

In the following, we use the concepts of a static database context and static schema context which designate the default database and schema names that are used to resolve names that are not fully qualified during both compilation and execution:

All unqualified schema bound object names (such as functions and table names) will be resolved against the current static schema context within the current static database context. Individual names can overwrite the resolution by using multi-part names (so called qualified names). E.g., T will be resolved against the current context, S.T will resolve the object name T in the schema S in the current static database context, and D.S.T will resolve the object name T in the schema S in the database D.

Note that names inside U-SQL functions are resolved based on the context during compilation of the function, and not the dynamic context during use.

All metadata objects except credentials are being created and managed with the following Data Definition Language (DDL) statements.

DDL Statements (U-SQL)

Syntax
DDL_Statement :=                                                                                         
    DB_DDL_Statement  
|   Schema_DDL_Statement  
|   Table_DDL_Statement  
|   Index_DDL_Statement  
|   Statistics_DDL_Statement  
|   View_DDL_Statement  
|   Function_DDL_Statement 
|   Package_DDL_Statement   
|   Procedure_DDL_Statement  
|   Assembly_DDL_Statement  
|   Datasource_DDL_Statement  
|   Type_DDL_Statement.

Credentials have to be created and managed with the credential management commandlets in the latest Azure Powershell. See Set-AzureRmDataLakeAnalyticsCatalogCredential for information on creating and managing an Azure Data Lake Analytics catalog credential.

See also

© 2018 Microsoft