Secure Zone Views | Data Dictionary | Teradata Vantage - Teradata Secure Zone Views - Advanced SQL Engine - Teradata Database

Data Dictionary

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
Published
June 2020
Language
English (United States)
Last Update
2020-10-15
dita:mapPath
yoz1556235523563.ditamap
dita:ditavalPath
lze1555437562152.ditaval
dita:id
B035-1092
lifecycle
previous
Product Category
Teradata Vantageā„¢

For Vantage systems configured with secure zones, data dictionary access is constrained by zone.

The data dictionary contains zone specific system views ending in _SZ for related Unicode and compatibility views. Zone specific views are not needed for VX views because they already contain security constraints in their definition that limit the result set to only the rows associated with the requesting user.

Even with Teradata Secure Zones configured, all users query the non _SZ views. Privileges are checked against the non _SZ view.

The following table shows data dictionary view access for the users.

User Data Dictionary View Access
  • DBC
  • Non-zone user with ZONE OVERRIDE
These users get system-wide information from views without zone filtration.

For example, if DBC or a non-zone user with ZONE OVERRIDE does a SELECT from the QryLogXMLV view, they will get information from the QryLogXMLV view without any filtration by zone.

  • Zone user
Access is constrained by zone.

For example, if a zone user does a SELECT from the QryLogXMLV view, information is returned from the zone constrained view.

  • Non-zone user without ZONE OVERRIDE
These users are restricted to non-zone dictionary data only.

The following views are constrained by zone.

  • DBC.AccessLog[V]
  • DBC.AccLogRules[V]
  • DBC.AccountInfo[V]
  • DBC.AllRights[V]
  • DBC.AllRoleRights[V]
  • DBC.AllSpace[V]
  • DBC.All_RI_Children[V]
  • DBC.All_RI_Parents[V]
  • DBC.AMPUsage[V]
  • DBC.ArchiveLoggingObjsV
  • DBC.Authoriziations[V]
  • DBC.BAR_ChildrenV
  • DBC.BAR_Databases2V
  • DBC.BAR_JoinIndicesV
  • DBC.BAR_ownerdbV
  • DBC.BAR_RI_Distinct_ParentsV
  • DBC.BAR_StatsV
  • DBC.BAR_Tables2V
  • DBC.BAR_TablesV
  • DBC.Children[V]
  • DBC.Columns[V]
  • DBC.ColumnsqV
  • DBC.ColumnsjqV
  • DBC.ColumnsUseCountV
  • DBC.ConnectRules[V]
  • DBC.ConstraintFunctionsV
  • DBC.Databases2[V]
  • DBC.Databases[V]
  • DBC.DatabaseUseCountV
  • DBC.Database_Default_Journals[V]
  • DBC.DBQLRules[V]
  • DBC.DeleteAccessLog[V]
  • DBC.DeleteUseCountV
  • DBC.DiskSpace[V]
  • DBC.ErrorTblsV
  • DBC.ExpStatsV
  • DBC.IndexConstraints[V]
  • DBC.IndexStatsV
  • DBC.IndexUseCountV
  • DBC.Indices[V]
  • DBC.InsertUseCountV
  • DBC.JoinIndicesV
  • DBC.Journals[V]
  • DBC.LoadTablesInfoV
  • DBC.LogOnOff[V]
  • DBC.LogonRules[V]
  • DBC.MapGrantsV[X]
  • DBC.MapsV[X]
  • DBC.MultiColumnStatsV
  • DBC.MultiExpStatsV
  • DBC.ObjectUseCountV
  • DBC.ownerdb[V]
  • DBC.PartitioningConstraintsV
  • DBC.PeriodsV
  • DBC.ProfileAsgdSecConstraintsV
  • DBC.ProfileInfo[V]
  • DBC.QryLockLogXMLV
  • DBC.QryLog[V]
  • DBC.QryLogExplain[V]
  • DBC.QryLogExplainDocV
  • DBC.QryLogObjects[V]
  • DBC.QryLogParamJSON
  • DBC.QryLogParamV
  • DBC.QryLogSQL[V]
  • DBC.QryLogSQLDocV
  • DBC.QryLogSteps[V]
  • DBC.QryLogSummary[V]
  • DBC.QryLogTDWM[V]
  • DBC.QryLogXMLDocV
  • DBC.QryLogUtilityV
  • DBC.QueryStatsV
  • DBC.ResolvedDTS[V]
  • DBC.RI_Child_Tables[V]
  • DBC.RI_Distinct_Children[V]
  • DBC.RI_Distinct_Parents[V]
  • DBC.RI_Parent_Tables[V]
  • DBC.RoleInfo[V]
  • DBC.RoleMembers[V]
  • DBC.SecConstraintsV
  • DBC.SecurityLog[V]
  • DBC.SessionInfo[V]
  • DBC.SHOWCOLCHECKS[V]
  • DBC.SHOWTBLCHECKS[V]
  • DBC.StatsV
  • DBC.StatUseCountV
  • DBC.Tables[V]
  • DBC.TableSize[V]
  • DBC.TableText[V]
  • DBC.Table_LevelConstraints[V]
  • DBC.TempTableStatsV
  • DBC.Triggers[V]
  • DBC.UpdateUseCountV
  • DBC.Userdb[V]
  • DBC.User_Default_Journals[V]
  • DBC.UsrAsgdSecConstraintsV
  • DBC.ViewStatsV
  • DBC.ZoneGuestsV
  • DBC.ZonesV

To see the secure zones views in the data dictionary, the Secure Zones feature must be enabled first. Contact your Teradata representative to enable this feature.