RENAME

In the Ultra Transcenders books

DP-900

Each book explains RENAME in context, with comparison tables and the common traps.

Terms in this definition

• Schema

  The middle part of a Unity Catalog name (catalog.schema.table), grouping tables, views, volumes, functions and models inside a catalog. A grant on it covers everything in it now and later, and nothing inside can be reached without USE SCHEMA.

• Event

  Table in Log Analytics where entries from Windows event logs are kept.

• DDL

  Data Definition Language, the SQL statements CREATE, ALTER, DROP and RENAME, used to make, change and delete database objects like tables and views.

Related terms

• Default-First-Site-Name

  Name given automatically to the first site in a new AD DS forest when its first DC is promoted; organisations frequently rename it after a real location.

• Default lakehouse

  Pinned to a notebook, it determines where relative Files/ and Tables/ paths and Spark SQL table names without a qualifier point. If you switch to another lakehouse or rename it, the session must be restarted.

• Fabric administrator

  Whoever holds this Entra role can govern Fabric and Power BI end to end, setting tenant options and looking after domains and workspaces. Until a 2023 rename, Microsoft called it Power BI administrator.

• logicalId

  An ID that Fabric generates and stores in each item's .platform file so Git can keep matching the item to its folder after a rename, and across workspaces. Leave it unchanged.

• Manage fields

  An Eventstream step for reshaping events: you can add, drop or rename fields and convert their types, and built-in functions handle strings, dates, times and maths.

• Microsoft-managed Conditional Access policies

  Policies Microsoft itself adds to qualifying tenants, all named with a Microsoft-managed: prefix. Each starts in report-only mode and is enforced after 30 days or more unless switched Off; you can adjust state and exclusions but not delete or rename them.