在Teradata中创建表命令中使用AMPs

我是Teradata的新手。有谁能告诉我AMPs在Teradata中创建任何表时有多大帮助。 让我们有一个场景。

---

我有一个4安培的Teradata数据库。我了解到，当我们将数据插入表中时，AMPs将非常有用。根据索引，它将在AMPs的帮助下分发数据。但是在创建表时，该命令只需要通过AMPs执行。因此，我想知道届时将使用哪个AMP？？？

在数据字典中实际创建表是一个行哈希级别的操作，涉及一个AMP将记录存储在DBC.TVM中。根据解释中列出的其他操作，可能还涉及其他放大器，但并非单一的全放大器操作。（这没有考虑数据的加载及其在各安培之间的分布。）

示例说明：

  1) First, we lock FUBAR.ABC for exclusive use. 
  2) Next, we lock a distinct DBC."pseudo table" for write on a RowHash
     for deadlock prevention, we lock a distinct DBC."pseudo table" for
     write on a RowHash for deadlock prevention, we lock a distinct
     DBC."pseudo table" for read on a RowHash for deadlock prevention,
     and we lock a distinct DBC."pseudo table" for write on a RowHash
     for deadlock prevention. 
  3) We lock DBC.DBase for read on a RowHash, we lock DBC.Indexes for
     write on a RowHash, we lock DBC.TVFields for write on a RowHash,
     we lock DBC.TVM for write on a RowHash, and we lock
     DBC.AccessRights for write on a RowHash. 
  4) We execute the following steps in parallel. 
       1) We do a single-AMP ABORT test from DBC.DBase by way of the
          unique primary index. 
       2) We do a single-AMP ABORT test from DBC.TVM by way of the
          unique primary index. 
       3) We do an INSERT into DBC.Indexes (no lock required). 
       4) We do an INSERT into DBC.TVFields (no lock required). 
       5) We do an INSERT into DBC.TVM (no lock required). 
       6) We INSERT default rights to DBC.AccessRights for FUBAR.ABC. 
  5) We create the table header. 
  6) Finally, we send out an END TRANSACTION step to all AMPs involved
     in processing the request.
  -> No rows are returned to the user as the result of statement 1. 

---

数据字典中表的实际创建是一个行哈希级别的操作，涉及一个AMP将记录存储在DBC.TVM中。根据解释中列出的其他操作，可能还涉及其他放大器，但并非单一的全放大器操作。（这没有考虑数据的加载及其在各安培之间的分布。）

示例说明：

  1) First, we lock FUBAR.ABC for exclusive use. 
  2) Next, we lock a distinct DBC."pseudo table" for write on a RowHash
     for deadlock prevention, we lock a distinct DBC."pseudo table" for
     write on a RowHash for deadlock prevention, we lock a distinct
     DBC."pseudo table" for read on a RowHash for deadlock prevention,
     and we lock a distinct DBC."pseudo table" for write on a RowHash
     for deadlock prevention. 
  3) We lock DBC.DBase for read on a RowHash, we lock DBC.Indexes for
     write on a RowHash, we lock DBC.TVFields for write on a RowHash,
     we lock DBC.TVM for write on a RowHash, and we lock
     DBC.AccessRights for write on a RowHash. 
  4) We execute the following steps in parallel. 
       1) We do a single-AMP ABORT test from DBC.DBase by way of the
          unique primary index. 
       2) We do a single-AMP ABORT test from DBC.TVM by way of the
          unique primary index. 
       3) We do an INSERT into DBC.Indexes (no lock required). 
       4) We do an INSERT into DBC.TVFields (no lock required). 
       5) We do an INSERT into DBC.TVM (no lock required). 
       6) We INSERT default rights to DBC.AccessRights for FUBAR.ABC. 
  5) We create the table header. 
  6) Finally, we send out an END TRANSACTION step to all AMPs involved
     in processing the request.
  -> No rows are returned to the user as the result of statement 1.