@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class MicrosoftSQLServerSettings extends Object implements Serializable, Cloneable, StructuredPojo
Provides information that defines a Microsoft SQL Server endpoint.
| Constructor and Description | 
|---|
| MicrosoftSQLServerSettings() | 
| Modifier and Type | Method and Description | 
|---|---|
| MicrosoftSQLServerSettings | clone() | 
| boolean | equals(Object obj) | 
| Integer | getBcpPacketSize()
 The maximum size of the packets (in bytes) used to transfer data using BCP. | 
| String | getControlTablesFileGroup()
 Specifies a file group for the DMS internal tables. | 
| String | getDatabaseName()
 Database name for the endpoint. | 
| Boolean | getForceLobLookup()
 Forces LOB lookup on inline LOB. | 
| String | getPassword()
 Endpoint connection password. | 
| Integer | getPort()
 Endpoint TCP port. | 
| Boolean | getQuerySingleAlwaysOnNode()
 Cleans and recreates table metadata information on the replication instance when a mismatch occurs. | 
| Boolean | getReadBackupOnly()
 When this attribute is set to  Y, DMS only reads changes from transaction log backups and doesn't
 read from the active transaction log file during ongoing replication. | 
| String | getSafeguardPolicy()
 Use this attribute to minimize the need to access the backup log and enable DMS to prevent truncation using one
 of the following two methods. | 
| String | getSecretsManagerAccessRoleArn()
 The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the
 required permissions to access the value in  SecretsManagerSecret. | 
| String | getSecretsManagerSecretId()
 The full ARN, partial ARN, or friendly name of the  SecretsManagerSecretthat contains the SQL Server
 endpoint connection details. | 
| String | getServerName()
 Fully qualified domain name of the endpoint. | 
| String | getTlogAccessMode()
 Indicates the mode used to fetch CDC data. | 
| Boolean | getTrimSpaceInChar()
 Use the  TrimSpaceInCharsource endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. | 
| Boolean | getUseBcpFullLoad()
 Use this to attribute to transfer data for full-load operations using BCP. | 
| String | getUsername()
 Endpoint connection user name. | 
| Boolean | getUseThirdPartyBackupDevice()
 When this attribute is set to  Y, DMS processes third-party transaction log backups if they are
 created in native format. | 
| int | hashCode() | 
| Boolean | isForceLobLookup()
 Forces LOB lookup on inline LOB. | 
| Boolean | isQuerySingleAlwaysOnNode()
 Cleans and recreates table metadata information on the replication instance when a mismatch occurs. | 
| Boolean | isReadBackupOnly()
 When this attribute is set to  Y, DMS only reads changes from transaction log backups and doesn't
 read from the active transaction log file during ongoing replication. | 
| Boolean | isTrimSpaceInChar()
 Use the  TrimSpaceInCharsource endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. | 
| Boolean | isUseBcpFullLoad()
 Use this to attribute to transfer data for full-load operations using BCP. | 
| Boolean | isUseThirdPartyBackupDevice()
 When this attribute is set to  Y, DMS processes third-party transaction log backups if they are
 created in native format. | 
| void | marshall(ProtocolMarshaller protocolMarshaller)Marshalls this structured data using the given  ProtocolMarshaller. | 
| void | setBcpPacketSize(Integer bcpPacketSize)
 The maximum size of the packets (in bytes) used to transfer data using BCP. | 
| void | setControlTablesFileGroup(String controlTablesFileGroup)
 Specifies a file group for the DMS internal tables. | 
| void | setDatabaseName(String databaseName)
 Database name for the endpoint. | 
| void | setForceLobLookup(Boolean forceLobLookup)
 Forces LOB lookup on inline LOB. | 
| void | setPassword(String password)
 Endpoint connection password. | 
| void | setPort(Integer port)
 Endpoint TCP port. | 
| void | setQuerySingleAlwaysOnNode(Boolean querySingleAlwaysOnNode)
 Cleans and recreates table metadata information on the replication instance when a mismatch occurs. | 
| void | setReadBackupOnly(Boolean readBackupOnly)
 When this attribute is set to  Y, DMS only reads changes from transaction log backups and doesn't
 read from the active transaction log file during ongoing replication. | 
| void | setSafeguardPolicy(String safeguardPolicy)
 Use this attribute to minimize the need to access the backup log and enable DMS to prevent truncation using one
 of the following two methods. | 
| void | setSecretsManagerAccessRoleArn(String secretsManagerAccessRoleArn)
 The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the
 required permissions to access the value in  SecretsManagerSecret. | 
| void | setSecretsManagerSecretId(String secretsManagerSecretId)
 The full ARN, partial ARN, or friendly name of the  SecretsManagerSecretthat contains the SQL Server
 endpoint connection details. | 
| void | setServerName(String serverName)
 Fully qualified domain name of the endpoint. | 
| void | setTlogAccessMode(String tlogAccessMode)
 Indicates the mode used to fetch CDC data. | 
| void | setTrimSpaceInChar(Boolean trimSpaceInChar)
 Use the  TrimSpaceInCharsource endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. | 
| void | setUseBcpFullLoad(Boolean useBcpFullLoad)
 Use this to attribute to transfer data for full-load operations using BCP. | 
| void | setUsername(String username)
 Endpoint connection user name. | 
| void | setUseThirdPartyBackupDevice(Boolean useThirdPartyBackupDevice)
 When this attribute is set to  Y, DMS processes third-party transaction log backups if they are
 created in native format. | 
| String | toString()Returns a string representation of this object. | 
| MicrosoftSQLServerSettings | withBcpPacketSize(Integer bcpPacketSize)
 The maximum size of the packets (in bytes) used to transfer data using BCP. | 
| MicrosoftSQLServerSettings | withControlTablesFileGroup(String controlTablesFileGroup)
 Specifies a file group for the DMS internal tables. | 
| MicrosoftSQLServerSettings | withDatabaseName(String databaseName)
 Database name for the endpoint. | 
| MicrosoftSQLServerSettings | withForceLobLookup(Boolean forceLobLookup)
 Forces LOB lookup on inline LOB. | 
| MicrosoftSQLServerSettings | withPassword(String password)
 Endpoint connection password. | 
| MicrosoftSQLServerSettings | withPort(Integer port)
 Endpoint TCP port. | 
| MicrosoftSQLServerSettings | withQuerySingleAlwaysOnNode(Boolean querySingleAlwaysOnNode)
 Cleans and recreates table metadata information on the replication instance when a mismatch occurs. | 
| MicrosoftSQLServerSettings | withReadBackupOnly(Boolean readBackupOnly)
 When this attribute is set to  Y, DMS only reads changes from transaction log backups and doesn't
 read from the active transaction log file during ongoing replication. | 
| MicrosoftSQLServerSettings | withSafeguardPolicy(SafeguardPolicy safeguardPolicy)
 Use this attribute to minimize the need to access the backup log and enable DMS to prevent truncation using one
 of the following two methods. | 
| MicrosoftSQLServerSettings | withSafeguardPolicy(String safeguardPolicy)
 Use this attribute to minimize the need to access the backup log and enable DMS to prevent truncation using one
 of the following two methods. | 
| MicrosoftSQLServerSettings | withSecretsManagerAccessRoleArn(String secretsManagerAccessRoleArn)
 The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the
 required permissions to access the value in  SecretsManagerSecret. | 
| MicrosoftSQLServerSettings | withSecretsManagerSecretId(String secretsManagerSecretId)
 The full ARN, partial ARN, or friendly name of the  SecretsManagerSecretthat contains the SQL Server
 endpoint connection details. | 
| MicrosoftSQLServerSettings | withServerName(String serverName)
 Fully qualified domain name of the endpoint. | 
| MicrosoftSQLServerSettings | withTlogAccessMode(String tlogAccessMode)
 Indicates the mode used to fetch CDC data. | 
| MicrosoftSQLServerSettings | withTlogAccessMode(TlogAccessMode tlogAccessMode)
 Indicates the mode used to fetch CDC data. | 
| MicrosoftSQLServerSettings | withTrimSpaceInChar(Boolean trimSpaceInChar)
 Use the  TrimSpaceInCharsource endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. | 
| MicrosoftSQLServerSettings | withUseBcpFullLoad(Boolean useBcpFullLoad)
 Use this to attribute to transfer data for full-load operations using BCP. | 
| MicrosoftSQLServerSettings | withUsername(String username)
 Endpoint connection user name. | 
| MicrosoftSQLServerSettings | withUseThirdPartyBackupDevice(Boolean useThirdPartyBackupDevice)
 When this attribute is set to  Y, DMS processes third-party transaction log backups if they are
 created in native format. | 
public void setPort(Integer port)
Endpoint TCP port.
port - Endpoint TCP port.public Integer getPort()
Endpoint TCP port.
public MicrosoftSQLServerSettings withPort(Integer port)
Endpoint TCP port.
port - Endpoint TCP port.public void setBcpPacketSize(Integer bcpPacketSize)
The maximum size of the packets (in bytes) used to transfer data using BCP.
bcpPacketSize - The maximum size of the packets (in bytes) used to transfer data using BCP.public Integer getBcpPacketSize()
The maximum size of the packets (in bytes) used to transfer data using BCP.
public MicrosoftSQLServerSettings withBcpPacketSize(Integer bcpPacketSize)
The maximum size of the packets (in bytes) used to transfer data using BCP.
bcpPacketSize - The maximum size of the packets (in bytes) used to transfer data using BCP.public void setDatabaseName(String databaseName)
Database name for the endpoint.
databaseName - Database name for the endpoint.public String getDatabaseName()
Database name for the endpoint.
public MicrosoftSQLServerSettings withDatabaseName(String databaseName)
Database name for the endpoint.
databaseName - Database name for the endpoint.public void setControlTablesFileGroup(String controlTablesFileGroup)
Specifies a file group for the DMS internal tables. When the replication task starts, all the internal DMS control tables (awsdms_ apply_exception, awsdms_apply, awsdms_changes) are created for the specified file group.
controlTablesFileGroup - Specifies a file group for the DMS internal tables. When the replication task starts, all the internal DMS
        control tables (awsdms_ apply_exception, awsdms_apply, awsdms_changes) are created for the specified file
        group.public String getControlTablesFileGroup()
Specifies a file group for the DMS internal tables. When the replication task starts, all the internal DMS control tables (awsdms_ apply_exception, awsdms_apply, awsdms_changes) are created for the specified file group.
public MicrosoftSQLServerSettings withControlTablesFileGroup(String controlTablesFileGroup)
Specifies a file group for the DMS internal tables. When the replication task starts, all the internal DMS control tables (awsdms_ apply_exception, awsdms_apply, awsdms_changes) are created for the specified file group.
controlTablesFileGroup - Specifies a file group for the DMS internal tables. When the replication task starts, all the internal DMS
        control tables (awsdms_ apply_exception, awsdms_apply, awsdms_changes) are created for the specified file
        group.public void setPassword(String password)
Endpoint connection password.
password - Endpoint connection password.public String getPassword()
Endpoint connection password.
public MicrosoftSQLServerSettings withPassword(String password)
Endpoint connection password.
password - Endpoint connection password.public void setQuerySingleAlwaysOnNode(Boolean querySingleAlwaysOnNode)
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.
querySingleAlwaysOnNode - 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.public Boolean getQuerySingleAlwaysOnNode()
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.
public MicrosoftSQLServerSettings withQuerySingleAlwaysOnNode(Boolean querySingleAlwaysOnNode)
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.
querySingleAlwaysOnNode - 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.public Boolean isQuerySingleAlwaysOnNode()
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.
public void setReadBackupOnly(Boolean readBackupOnly)
 When this attribute is set to Y, 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.
 
readBackupOnly - When this attribute is set to Y, 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.public Boolean getReadBackupOnly()
 When this attribute is set to Y, 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.
 
Y, 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.public MicrosoftSQLServerSettings withReadBackupOnly(Boolean readBackupOnly)
 When this attribute is set to Y, 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.
 
readBackupOnly - When this attribute is set to Y, 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.public Boolean isReadBackupOnly()
 When this attribute is set to Y, 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.
 
Y, 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.public void setSafeguardPolicy(String safeguardPolicy)
Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
safeguardPolicy - Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
SafeguardPolicypublic String getSafeguardPolicy()
Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
Start transactions in the database: This is the default method. When this method is used, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
SafeguardPolicypublic MicrosoftSQLServerSettings withSafeguardPolicy(String safeguardPolicy)
Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
safeguardPolicy - Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
SafeguardPolicypublic MicrosoftSQLServerSettings withSafeguardPolicy(SafeguardPolicy safeguardPolicy)
Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
safeguardPolicy - Use this attribute to minimize the need to access the backup log and enable 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, 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, 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 DMS task can access the database at any given time. Therefore, if you need to run parallel DMS tasks against the same database, use the default method.
SafeguardPolicypublic void setServerName(String serverName)
 Fully qualified domain name of the endpoint. For an Amazon RDS SQL Server instance, this is the output of DescribeDBInstances,
 in the
  Endpoint.Address
 field.
 
serverName - Fully qualified domain name of the endpoint. For an Amazon RDS SQL Server instance, this is the output of
        
        DescribeDBInstances, in the
         Endpoint.Address
        field.public String getServerName()
 Fully qualified domain name of the endpoint. For an Amazon RDS SQL Server instance, this is the output of DescribeDBInstances,
 in the
  Endpoint.Address
 field.
 
 Endpoint.Address
         field.public MicrosoftSQLServerSettings withServerName(String serverName)
 Fully qualified domain name of the endpoint. For an Amazon RDS SQL Server instance, this is the output of DescribeDBInstances,
 in the
  Endpoint.Address
 field.
 
serverName - Fully qualified domain name of the endpoint. For an Amazon RDS SQL Server instance, this is the output of
        
        DescribeDBInstances, in the
         Endpoint.Address
        field.public void setUsername(String username)
Endpoint connection user name.
username - Endpoint connection user name.public String getUsername()
Endpoint connection user name.
public MicrosoftSQLServerSettings withUsername(String username)
Endpoint connection user name.
username - Endpoint connection user name.public void setUseBcpFullLoad(Boolean useBcpFullLoad)
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.
useBcpFullLoad - 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.public Boolean getUseBcpFullLoad()
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.
public MicrosoftSQLServerSettings withUseBcpFullLoad(Boolean useBcpFullLoad)
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.
useBcpFullLoad - 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.public Boolean isUseBcpFullLoad()
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.
public void setUseThirdPartyBackupDevice(Boolean useThirdPartyBackupDevice)
 When this attribute is set to Y, DMS processes third-party transaction log backups if they are
 created in native format.
 
useThirdPartyBackupDevice - When this attribute is set to Y, DMS processes third-party transaction log backups if they
        are created in native format.public Boolean getUseThirdPartyBackupDevice()
 When this attribute is set to Y, DMS processes third-party transaction log backups if they are
 created in native format.
 
Y, DMS processes third-party transaction log backups if they
         are created in native format.public MicrosoftSQLServerSettings withUseThirdPartyBackupDevice(Boolean useThirdPartyBackupDevice)
 When this attribute is set to Y, DMS processes third-party transaction log backups if they are
 created in native format.
 
useThirdPartyBackupDevice - When this attribute is set to Y, DMS processes third-party transaction log backups if they
        are created in native format.public Boolean isUseThirdPartyBackupDevice()
 When this attribute is set to Y, DMS processes third-party transaction log backups if they are
 created in native format.
 
Y, DMS processes third-party transaction log backups if they
         are created in native format.public void setSecretsManagerAccessRoleArn(String secretsManagerAccessRoleArn)
 The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the
 required permissions to access the value in SecretsManagerSecret. The role must allow the
 iam:PassRole action. SecretsManagerSecret has the value of the Amazon Web Services
 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 Database Migration Service resources in the Database Migration Service User Guide.
 
secretsManagerAccessRoleArn - The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants
        the required permissions to access the value in SecretsManagerSecret. The role must allow the
        iam:PassRole action. SecretsManagerSecret has the value of the Amazon Web
        Services 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 Database Migration Service resources in the Database Migration Service
        User Guide.
        
public String getSecretsManagerAccessRoleArn()
 The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the
 required permissions to access the value in SecretsManagerSecret. The role must allow the
 iam:PassRole action. SecretsManagerSecret has the value of the Amazon Web Services
 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 Database Migration Service resources in the Database Migration Service User Guide.
 
SecretsManagerSecret. The role must allow
         the iam:PassRole action. SecretsManagerSecret has the value of the Amazon Web
         Services 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 Database Migration Service resources in the Database Migration Service
         User Guide.
         
public MicrosoftSQLServerSettings withSecretsManagerAccessRoleArn(String secretsManagerAccessRoleArn)
 The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants the
 required permissions to access the value in SecretsManagerSecret. The role must allow the
 iam:PassRole action. SecretsManagerSecret has the value of the Amazon Web Services
 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 Database Migration Service resources in the Database Migration Service User Guide.
 
secretsManagerAccessRoleArn - The full Amazon Resource Name (ARN) of the IAM role that specifies DMS as the trusted entity and grants
        the required permissions to access the value in SecretsManagerSecret. The role must allow the
        iam:PassRole action. SecretsManagerSecret has the value of the Amazon Web
        Services 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 Database Migration Service resources in the Database Migration Service
        User Guide.
        
public void setSecretsManagerSecretId(String secretsManagerSecretId)
 The full ARN, partial ARN, or friendly name of the SecretsManagerSecret that contains the SQL Server
 endpoint connection details.
 
secretsManagerSecretId - The full ARN, partial ARN, or friendly name of the SecretsManagerSecret that contains the SQL
        Server endpoint connection details.public String getSecretsManagerSecretId()
 The full ARN, partial ARN, or friendly name of the SecretsManagerSecret that contains the SQL Server
 endpoint connection details.
 
SecretsManagerSecret that contains the
         SQL Server endpoint connection details.public MicrosoftSQLServerSettings withSecretsManagerSecretId(String secretsManagerSecretId)
 The full ARN, partial ARN, or friendly name of the SecretsManagerSecret that contains the SQL Server
 endpoint connection details.
 
secretsManagerSecretId - The full ARN, partial ARN, or friendly name of the SecretsManagerSecret that contains the SQL
        Server endpoint connection details.public void setTrimSpaceInChar(Boolean trimSpaceInChar)
 Use the TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. Setting TrimSpaceInChar does not left-trim data. The default value is
 true.
 
trimSpaceInChar - Use the TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data
        types during migration. Setting TrimSpaceInChar does not left-trim data. The default value is
        true.public Boolean getTrimSpaceInChar()
 Use the TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. Setting TrimSpaceInChar does not left-trim data. The default value is
 true.
 
TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data
         types during migration. Setting TrimSpaceInChar does not left-trim data. The default value
         is true.public MicrosoftSQLServerSettings withTrimSpaceInChar(Boolean trimSpaceInChar)
 Use the TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. Setting TrimSpaceInChar does not left-trim data. The default value is
 true.
 
trimSpaceInChar - Use the TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data
        types during migration. Setting TrimSpaceInChar does not left-trim data. The default value is
        true.public Boolean isTrimSpaceInChar()
 Use the TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data types
 during migration. Setting TrimSpaceInChar does not left-trim data. The default value is
 true.
 
TrimSpaceInChar source endpoint setting to right-trim data on CHAR and NCHAR data
         types during migration. Setting TrimSpaceInChar does not left-trim data. The default value
         is true.public void setTlogAccessMode(String tlogAccessMode)
Indicates the mode used to fetch CDC data.
tlogAccessMode - Indicates the mode used to fetch CDC data.TlogAccessModepublic String getTlogAccessMode()
Indicates the mode used to fetch CDC data.
TlogAccessModepublic MicrosoftSQLServerSettings withTlogAccessMode(String tlogAccessMode)
Indicates the mode used to fetch CDC data.
tlogAccessMode - Indicates the mode used to fetch CDC data.TlogAccessModepublic MicrosoftSQLServerSettings withTlogAccessMode(TlogAccessMode tlogAccessMode)
Indicates the mode used to fetch CDC data.
tlogAccessMode - Indicates the mode used to fetch CDC data.TlogAccessModepublic void setForceLobLookup(Boolean forceLobLookup)
Forces LOB lookup on inline LOB.
forceLobLookup - Forces LOB lookup on inline LOB.public Boolean getForceLobLookup()
Forces LOB lookup on inline LOB.
public MicrosoftSQLServerSettings withForceLobLookup(Boolean forceLobLookup)
Forces LOB lookup on inline LOB.
forceLobLookup - Forces LOB lookup on inline LOB.public Boolean isForceLobLookup()
Forces LOB lookup on inline LOB.
public String toString()
toString in class ObjectObject.toString()public MicrosoftSQLServerSettings clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojoProtocolMarshaller.marshall in interface StructuredPojoprotocolMarshaller - Implementation of ProtocolMarshaller used to marshall this object's data.