Transfer of Space Allocation | SQL Data Control Language | VantageCloud Lake - Transfer of Space Allocation - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
Language
English (United States)
Last Update
2024-04-03
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
A transfer of ownership also transfers the permanent space allocated to the named database or user. This affects space allocation in the system as follows:
  • The aggregate number of permanent space bytes available to the former owners (the owner who submits the GIVE statement plus the owners above this owner in the hierarchy) is reduced by the number of permanent space bytes in the transferred database. This includes total space allocated to the database, plus that of all databases and users owned by the transferred database.
  • If the transferred database is dropped, then the number of bytes of permanent space allocated to the new immediate owner of the transferred database is increased by the number of bytes of permanent space in the transferred database. In addition, the aggregate number of bytes of permanent space available to owners above this owner in the hierarchy is increased by the number of bytes of permanent space that had been allocated to the transferred database.

For example, consider the following hierarchy:



If ownership of database C is transferred to database D, the structure of the hierarchy changes as follows:



When database C is transferred:
  • Database F, which is owned by C, is also transferred.
  • The number of permanent space bytes allocated to database A remains the same, but the aggregate number of permanent space bytes available to database A is reduced by 50 (the total number of permanent space bytes allocated to databases C and F).
  • The number of bytes allocated to databases D and B remains the same.
  • The available number of permanent space bytes, however, is increased by 50. That is, if databases C and F were dropped, the bytes allocated to C and F are transferred to database D.
  • A no longer has implicit privileges on C and F.
  • B and D now have implicit privileges on C and F.
  • Explicit privileges held by any of the databases or users do not change.

    For example, if A granted itself explicit privileges on C, or F, or on objects they contain, A still has those explicit privileges after submitting the GIVE statement.