Bobcares

Enable validation feature in AWS DMS – How to do

by | Jul 29, 2021

Wondering how to enable validation feature in AWS DMS? We can help you!

Here at Bobcares, we often get requests from our customers to Enable validation feature in their AWS instance.

Today let’s see how our Support Engineers do this set up for our customers as a part of our Server Management Services.

How to enable validation feature in AWS DMS (Database Migration Service)

Following are the steps that our Support Engineers follow to enable validation on a new task and and existing task:

Enabling validation on a new task

1. Firstly we must open the AWS DMS console, and go to Database migration tasks.

2. Then click on Create task.

3. And enter the details for Task configuration and Task settings.

4. After that from the Task settings section, select Enable validation and Enable CloudWatch logs.

5. If needed we can configure the Advanced task settings.

6. Finally, click on Create task.

Enabling validation on an existing task

1. Firstly, we must open the AWS DMS console, and go to Database migration tasks.

2. Then select the task, and check it status to see if it’s Failed or Stopped.

3. After that go to Actions, and click on Modify.

4. Now, from the Task settings section, check Enable validation.

5. Finally click on Save.

Viewing the results of the validation

1. Firstly, we must open the AWS DMS console, and go to Database migration tasks.

2. Select the name of task.

3. And go to Table statistics section, review the results.

Re-validating tables in a task

1. Firstly, we must open the AWS DMS console, and go to Database migration tasks.

2. Select the name of task.

3. And go to Table statistics section, select the table and click on Validate again.

4. For reviewing the validation metrics, go to Database migration tasks.

5. And select the name of the task, review the Migration task metrics section.

Some Limitations of enabling validation:

1. Data validation requires the table to have a primary key or unique index.

  • Primary key columns can’t be of type CLOBBLOB, or BYTE.
  • For primary key columns of type VARCHAR or CHAR, the length must be less than 1024.

2. Data validation generates additional queries against the source and target databases. We must ensure that both databases have enough resources to handle this additional load.

3. Data validation isn’t supported if a migration uses customized filtering or when consolidating several databases into one.

4. If one or more rows are being continuously modified during the validation, then AWS DMS can’t validate those rows. However, we can validate those rows manually, after the task completes.

5. Furthermore, AWS DMS do not support data validation of views.

[Need assistance? We can help you]

Conclusion

To conclude, we saw the steps that our Support Techs follow to enable validation feature in AWS DMS for our customers using AWS.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF