Hi
One of my jobs refreshes the datamart using ODBC enterprise stage's truncate and write option.The job runs for about 10 minutes during which the data gets deleted and loaded and user sees an inconsistent data.
Is it any way possible to see the old data in the table during the run time ,and after the load is completed see the new data.
Thanks
Arif
Avoiding Data disappear
Moderators: chulett, rschirm, roy
Exactly, this is called mirroring. It is infact pretty easy to achieve this through materialised views. Maintain a materialised view for your table and make sure that users always hit the materialized view. Refresh the view after each load.chulett wrote:Or load a second copy of the table and when the load completes, swap it in for the original.
Hope this helps :D
It took me fifteen years to discover I had no talent for ETL, but I couldn't give it up because by that time I was too famous.
-
- Charter Member
- Posts: 87
- Joined: Sat Mar 18, 2006 11:45 pm
Thanks for helpsud wrote:Exactly, this is called mirroring. It is infact pretty easy to achieve this through materialised views. Maintain a materialised view for your table and make sure that users always hit the materialized view. Refresh the view after each load.chulett wrote:Or load a second copy of the table and when the load completes, swap it in for the original.
Hope this helps :D
Can this be done through Data Stage also.
Arif
Yes , what you can do is create a procedure to refresh the materialised view and call this procedure in the close command of your target stage in the job or call the procedure through datastage after the loading job finishes. Since your users will always be hitting the materialised view, they will see the updated data.
It took me fifteen years to discover I had no talent for ETL, but I couldn't give it up because by that time I was too famous.
-
- Charter Member
- Posts: 87
- Joined: Sat Mar 18, 2006 11:45 pm
Thankssud wrote:Yes , what you can do is create a procedure to refresh the materialised view and call this procedure in the close command of your target stage in the job or call the procedure through datastage after the loading job finishes. Since your users will always be hitting the materialised view, they will see the updated data.
That was helpful