BcpPacketSize => Int

The maximum size of the packets (in bytes) used to transfer data using BCP.

ControlTablesFileGroup => Str

Specifies a file group for the AWS DMS internal tables. When the replication task starts, all the internal AWS DMS control tables (awsdms_ apply_exception, awsdms_apply, awsdms_changes) are created for the specified file group.

DatabaseName => Str

Database name for the endpoint.

Password => Str

Endpoint connection password.

Port => Int

Endpoint TCP port.

QuerySingleAlwaysOnNode => Bool

Cleans and recreates table metadata information on the replication instance when a mismatch occurs. An example is a situation where running an alter DDL statement on a table might result in different information about the table cached in the replication instance.

ReadBackupOnly => Bool

When this attribute is set to "Y", AWS DMS only reads changes from transaction log backups and doesn't read from the active transaction log file during ongoing replication. Setting this parameter to "Y" enables you to control active transaction log file growth during full load and ongoing replication tasks. However, it can add some source latency to ongoing replication.

SafeguardPolicy => Str

Use this attribute to minimize the need to access the backup log and enable AWS DMS to prevent truncation using one of the following two methods.

Start transactions in the database: This is the default method. When this method is used, AWS DMS prevents TLOG truncation by mimicking a transaction in the database. As long as such a transaction is open, changes that appear after the transaction started aren't truncated. If you need Microsoft Replication to be enabled in your database, then you must choose this method.

Exclusively use sp_repldone within a single task: When this method is used, AWS DMS reads the changes and then uses sp_repldone to mark the TLOG transactions as ready for truncation. Although this method doesn't involve any transactional activities, it can only be used when Microsoft Replication isn't running. Also, when using this method, only one AWS DMS task can access the database at any given time. Therefore, if you need to run parallel AWS DMS tasks against the same database, use the default method.

SecretsManagerAccessRoleArn => Str

The full Amazon Resource Name (ARN) of the IAM role that specifies AWS DMS as the trusted entity and grants the required permissions to access the value in "SecretsManagerSecret". "SecretsManagerSecret" has the value of the AWS Secrets Manager secret that allows access to the SQL Server endpoint.

You can specify one of two sets of values for these permissions. You can specify the values for this setting and "SecretsManagerSecretId". Or you can specify clear-text values for "UserName", "Password", "ServerName", and "Port". You can't specify both. For more information on creating this "SecretsManagerSecret" and the "SecretsManagerAccessRoleArn" and "SecretsManagerSecretId" required to access it, see Using secrets to access AWS Database Migration Service resources (https://docs.aws.amazon.com/https:/docs.aws.amazon.com/dms/latest/userguide/CHAP_Security.html#security-iam-secretsmanager) in the AWS Database Migration Service User Guide.

SecretsManagerSecretId => Str

The full ARN, partial ARN, or friendly name of the "SecretsManagerSecret" that contains the SQL Server endpoint connection details.

ServerName => Str

Fully qualified domain name of the endpoint.

UseBcpFullLoad => Bool

Use this to attribute to transfer data for full-load operations using BCP. When the target table contains an identity column that does not exist in the source table, you must disable the use BCP for loading table option.

Username => Str

Endpoint connection user name.

UseThirdPartyBackupDevice => Bool

When this attribute is set to "Y", DMS processes third-party transaction log backups if they are created in native format.