Join the social network of Tech Nerds, increase skill rank, get work, manage projects...
 
Node is saved as draft in My Content >> Draft
  • Dirty Table Feature In MDM

    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 0
    • 1.35k
    Comment on it

    Dirty Table Feature In MDM :

    Dirty Table is a system Table created to hold the dirty record which needs to Tokenize during Load, Merge, SIF Calls,put, update.

    It contain Only Column named ROWID_OBJECT.

    Whenever New Record Is Created the Entry goes to The Dirty Table which Signifies that this Record is Dirty and this Need to be Tokenize in the Next Tokenization Run.

    Why we need Dirty Table?

    • Removes the Locking Issue On Parent which the Child Record becomes Dirty.
    • Better Manageability of Product.
    • Better Performance, Since Dirty Table Remove the Locking Issue.

    How the MDM Hub Console Update The Dirty Table ?

    For each unique ROWID_OBJECT in the dirty table,

    • the tokenize process produces match tokens, and
    • then cleans up the dirty table.

    Lets See the Following Steps to Get a clear View :

    • Launch The MDM Hub Console.
    • Enter your Credentials.
    • Select the ORS table For Performing Updation.
    • Let us Assume that We have created Base Object (BO) table, Staging Table (ST) for two different source System, and Landing Table (LT).
    • We have insert Records in the Landing Table using import Operation.
    • Till Base Object table Don't contain Any Records , we can see in the Dirty_Table that Only Empty ROWID_OBJECT column can be Seen.
    • Now Perform Stage Operation means Loading Data from Landing Table(LT) to Staging Table(ST).
    • Then Perform Load Operation means Loading Data from Landing Table(ST) to Base Object (BO).
    • Now We can see some Records inserted into the Base Object (BO) table and Simultaneously we can check Dirty _Table will also contain some Record which become Dirty, this need to be Tokenize.

    • Now Perform Generate Match Token in the MDM Hub Console, to perform Tokenize Job.
    • This Tokenize job will generate match tokens from the Dirty Table. And we can see Matched token Generated in the STRP table.

    • After this, Dirty Table will become Empty.
    • Now Lets Perform Updation in the Record.
    • After Updation from SOAP UI, check the Dirty Table, we can see some Records in the ROWID_OBJECT column which now contains some records which are Dirty and Needs to be Tokenize Again .
    • In this way, Dirty Table works in MDM Hub Console whenever any existing or new Records needs to be Updation.
    Dirty Table in MDM MDM Dirty Table

 0 Comment(s)

Sign In
                           OR                           
                           OR                           
Register

Sign up using

                           OR                           
Forgot Password
Fill out the form below and instructions to reset your password will be emailed to you:
Reset Password
Fill out the form below and reset your password: