DQS (Data Quality Services) - Why Use DQS versus T-SQL Code to Cleanup data

  • I've been reading about DQA (Data Quality Services) in SQl 2012 and even installe dit and played around some with a few domain rules in a test DQS KB I created. The question I have that I can't find an answer for is why use DQS versus something like T-SQL in a SQL JOb?

    EXAMPLE:

    Lets say I routinely get data (to import) that contains errors in the Invoice Number field where sometimes there will be a dash brekaing up the number or a space or any other character. I want just the invoice number with no spaces or extra characters.

    I could use DQS to do this but why would I choose to use DQS versus using my own DML commands that I either have in a SQL Job or that are save dto file that I run manually whenever I get a new set fo data to cleanup and import.

    I've walked thru setting up a DQS KB and some Domain Rules and tested them and I can see the appeal. What I can't see is what benefit you get using DQS if you know T-SQL? Is DQS targeted at those persons who do data cleanup and do not know T-SQL and are therefore dependent on using something like Excel to celan up the data?

    Any thoughts or links would be most welcome as I am very interested in DQS but iit seems like a look of setup and extra work for something that can be done more easily using T-SQL.

    Thanks

    Kindest Regards,

    Just say No to Facebook!
  • Hi

    Just starting looking at DQS and found your post.

    Do you still use DQS ?

    Is it working well for you etc..

     

    Kevin

    Kevin

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply