AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
The
This operation only applies to Version
2019.11.21 (Current) of global tables.
DynamoDB might continue to accept data read and write operations, such as DeleteTable operation deletes a table and all of its items. After a DeleteTable
request, the specified table is in the DELETING state until DynamoDB completes
the deletion. If the table is in the ACTIVE state, you can delete it. If a
table is in CREATING or UPDATING states, then DynamoDB returns a ResourceInUseException.
If the specified table does not exist, DynamoDB returns a ResourceNotFoundException.
If table is already in the DELETING state, no error is returned.
GetItem
and PutItem, on a table in the DELETING state until the table deletion
is complete.
When you delete a table, any indexes on that table are also deleted.
If you have DynamoDB Streams enabled on the table, then the corresponding stream on
that table goes into the DISABLED state, and the stream is automatically deleted
after 24 hours.
Use the DescribeTable action to check the status of the table.
This is an asynchronous operation using the standard naming convention for .NET 4.5 or higher. For .NET 3.5 the operation is implemented as a pair of methods using the standard naming convention of BeginDeleteTable and EndDeleteTable.
Namespace: Amazon.DynamoDBv2
Assembly: AWSSDK.DynamoDBv2.dll
Version: 3.x.y.z
public abstract Task<DeleteTableResponse> DeleteTableAsync( String tableName, CancellationToken cancellationToken )
The name of the table to delete. You can also provide the Amazon Resource Name (ARN) of the table in this parameter.
A cancellation token that can be used by other objects or threads to receive notice of cancellation.
| Exception | Condition |
|---|---|
| InternalServerErrorException | An error occurred on the server side. |
| LimitExceededException | There is no limit to the number of daily on-demand backups that can be taken. For most purposes, up to 500 simultaneous table operations are allowed per account. These operations include CreateTable, UpdateTable, DeleteTable,UpdateTimeToLive, RestoreTableFromBackup, and RestoreTableToPointInTime. When you are creating a table with one or more secondary indexes, you can have up to 250 such requests running at a time. However, if the table or index specifications are complex, then DynamoDB might temporarily reduce the number of concurrent operations. When importing into DynamoDB, up to 50 simultaneous import table operations are allowed per account. There is a soft account quota of 2,500 tables. GetRecords was called with a value of more than 1000 for the limit request parameter. More than 2 processes are reading from the same streams shard at the same time. Exceeding this limit may result in request throttling. |
| ResourceInUseException | The operation conflicts with the resource's availability. For example, you attempted to recreate an existing table, or tried to delete a table currently in the CREATING state. |
| ResourceNotFoundException | The operation tried to access a nonexistent table or index. The resource might not be specified correctly, or its status might not be ACTIVE. |
.NET Core App:
Supported in: 3.1
.NET Standard:
Supported in: 2.0
.NET Framework:
Supported in: 4.5