Update-driven approach is chosen

View previous topic View next topic Go down

Update-driven approach is chosen

Post  aashaya m on Mon Nov 14, 2011 1:00 pm

a. Update-driven approach is chosen rather than query driven approach while integrating multiple heterogeneous information sources.justify whether true or false ?

b. Describe benefits and drawbacks of a source-driven architecture for gathering of data at a data warehouse , as compared to a destination-driven architecture ..

aashaya m

Posts : 18
Join date : 2011-04-25

View user profile

Back to top Go down

Re: Update-driven approach is chosen

Post  ngalemmo on Mon Nov 14, 2011 1:23 pm

Is this a test?
avatar
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

View user profile http://aginity.com

Back to top Go down

Yes sir......

Post  aashaya m on Tue Nov 15, 2011 12:35 am

Yes sir...in our Elective we do have Data warehousing ..but little bit confused about these questions ..you have any hint please reply

aashaya m

Posts : 18
Join date : 2011-04-25

View user profile

Back to top Go down

Re: Update-driven approach is chosen

Post  ngalemmo on Tue Nov 15, 2011 10:54 am

My guess is question A is asking which is better: handling integration at query time or when loading the DW.

Also not completely sure about B but I suspect the question is about what drives the design: the data available from the sources or the stated requirements of the mart.

It would be easier to understand the questions if I heard the lecture...
avatar
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

View user profile http://aginity.com

Back to top Go down

Re: Update-driven approach is chosen

Post  BoxesAndLines on Tue Nov 15, 2011 11:39 am

Nice questions. At least folks are starting to think about these types of things.
avatar
BoxesAndLines

Posts : 1212
Join date : 2009-02-03
Location : USA

View user profile

Back to top Go down

Re: Update-driven approach is chosen

Post  Jeff Smith on Wed Dec 14, 2011 5:05 pm

B sounds like comparing the pros and cons of Star Schema Vs 3nf. Leaving data in tables based on the source system rather thaa integrating the data from the various source systems into the same tables.

One is easier to build but harder to use. The other is easier to use but harder to build. One gets data quicker to the end user but forces the user to do a lot more stuff to the data in order to use it. The other takes time to build, harder to get real time data to user, but is a lot easier for the user to actually put into use.

Jeff Smith

Posts : 471
Join date : 2009-02-03

View user profile

Back to top Go down

Re: Update-driven approach is chosen

Post  ngalemmo on Wed Dec 14, 2011 6:41 pm

Agree. Replicating 3nf models is just a easy way to push the problem onto another group, in this case the users and/or reporting team. Its an expensive way to save a few bucks up front.
avatar
ngalemmo

Posts : 3000
Join date : 2009-05-15
Location : Los Angeles

View user profile http://aginity.com

Back to top Go down

Re: Update-driven approach is chosen

Post  Jeff Smith on Thu Dec 15, 2011 11:02 am

I am not sure it's about saving a few bucks. I think it's about implementing the fastest and easiest solution. End User pain doesn't fit into the traditional IT equation. I see it all the time. A report that takes 3 minutes to run is preferable over a report that needs a new aggregate table to run in 5 seconds.

Jeff Smith

Posts : 471
Join date : 2009-02-03

View user profile

Back to top Go down

Re: Update-driven approach is chosen

Post  Sponsored content


Sponsored content


Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum