Oracle Analytics

Get Involved. Join the Conversation.

Topic

    Brian Hall
    DATA-SYNC FiltersAnswered
    Topic posted April 16, 2019 by Brian HallSilver Medal: 2,000+ Points, last edited September 11, 2019, tagged Access & Manage Data, Home & Catalog, Packaging & Licensing, Reporting 
    75 Views, 1 Comment
    Title:
    DATA-SYNC Filters
    Summary:
    Need information about the Load Strategy Filters
    Content:

    I need information in regards to the Data Sync / Load Strategy/ Filters.  How do the filters work.  What function do they serve?  Are there any details that can be altered in regards to these filters? 

    Also, is there anyway to see what is taking place when the rows are being staged / copied up to the cloud?  Debug functions?

    Version:
    Oracle Analytics Cloud Data Sync (2.5)

    Best Comment

    Brian Hall

    FOUND WHAT i NEEDED  

    Load Strategies

    A load strategy defines how your data is loaded from a specific data source into your target. When you choose a load strategy that incrementally loads the data, Data Sync requires you to define a user key to uniquely identify a record on the target side, and a DATE/TIMESTAMP based column which can be used to identify the incremental data. If an index is not available, then Data Sync prompts you to create an index.

    An example load strategy

    You have a table with CONTACT_ID as the unique identifier for any record, and a date column LAST_UPD whose value is updated to the current timestamp whenever a record is created or updated. Here, you would choose CONTACT_ID for user key and LAST_UPD column as the Filter.

    When data is loaded for the first time, Data Sync issues a SELECT * FROM CONTACT statement. If the first load happened on January 1, 2014 at 10:00 AM, the subsequent load would issue the following SQL statement (Oracle syntax): SELECT * FROM CONTACT WHERE LAST_UPD > TO_DATE('01-01-2014 10:00', 'MM-DD-YYYY HH24:MI'). The record set then compares the CONTACT_ID value to the data already existing in the Oracle Business Intelligence Cloud Service schema. Any record without a match is inserted. Any records with a match are updated. It is important that the source system contains an index for the incremental filter column.

    Comment

     

    • Brian Hall

      FOUND WHAT i NEEDED  

      Load Strategies

      A load strategy defines how your data is loaded from a specific data source into your target. When you choose a load strategy that incrementally loads the data, Data Sync requires you to define a user key to uniquely identify a record on the target side, and a DATE/TIMESTAMP based column which can be used to identify the incremental data. If an index is not available, then Data Sync prompts you to create an index.

      An example load strategy

      You have a table with CONTACT_ID as the unique identifier for any record, and a date column LAST_UPD whose value is updated to the current timestamp whenever a record is created or updated. Here, you would choose CONTACT_ID for user key and LAST_UPD column as the Filter.

      When data is loaded for the first time, Data Sync issues a SELECT * FROM CONTACT statement. If the first load happened on January 1, 2014 at 10:00 AM, the subsequent load would issue the following SQL statement (Oracle syntax): SELECT * FROM CONTACT WHERE LAST_UPD > TO_DATE('01-01-2014 10:00', 'MM-DD-YYYY HH24:MI'). The record set then compares the CONTACT_ID value to the data already existing in the Oracle Business Intelligence Cloud Service schema. Any record without a match is inserted. Any records with a match are updated. It is important that the source system contains an index for the incremental filter column.