how to validate data before we do data mapping or migration

Question

0.00/5 (No votes)

See more:

I have task where i need to move data from one table1 to table2, i have source columns and destination columns but before i move data is it possible to find out is there any data in source column doesn't not fit destination column because of destination field type difference or field length is less like that ?

Like in a scenario i have source column which is char(1) and i am trying to map that column data to int column, here most of rows in source column have integer values but there are some alpha characters in some rows so i want to find out all those rows which are going to fail....the logic should work for all data types.

Thanks in advance!!

Posted 29-Nov-14 3:45am

l6it896

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maciej Los · Answer 1 · 2014-11-29T05:39:00

Have a look here: On Error Resume Next SQL Server 2005[^]

But you should know that there is no something like "the golden rule" for this kind of functionality. There is only one person who can write it: YOU! So, write validation rules depending on your needs.

Here is an idea for CHAR(1) to INT conversion:

SQL

SELECT CONVERT(INT, AkaIntField) AS NewInt
FROM (
    SELECT AkaIntField
    FROM TableName
    WHERE ISNUMERIC(AkaIntField)=1
) AS T