ravi kumar guturi

• Oct 4th, 2005

 

bottom approach is the best because in 3 tier architecture datatier is the bottom one.

snrv

 Profile Answers by snrv 

• Oct 27th, 2005

 

Top/down approach is better in datawarehousing

Rajesh.A

• Nov 18th, 2005

 

Rajesh: Bottom/Up approach is better

vivek barsagadey

• Nov 19th, 2005

 

At the time of software intragartion buttom/up is good but implimentatino time top/down is good.

sithusithu

 Profile Answers by sithusithu 

• Jan 20th, 2006

 

top down

ODS-->ETL-->Datawarehouse-->Datamart-->OLAP

Bottom up

ODS-->ETL-->Datamart-->Datawarehouse-->OLAP

Cheers,

Sithu

gazulas

 Profile Answers by gazulas Questions by gazulas

• Jan 29th, 2006

 

in top down approch: first we have to build dataware house then we will build data marts. which will need more crossfunctional skills and timetaking process also costly.

in bottom up approach: first we will build data marts then data warehuse. the data mart that is first build will remain as a proff of concept for the others. less time as compared to above and less cost.

kalam

• Feb 12th, 2006

 

Nothing wrong with any of these approaches. It all depends on your business requirements and what is in place already at your company. Lot of folks have a hybrid approach. For more info read Kimball vs Inmon..

samirdesai999

 Profile Answers by samirdesai999 

• Jun 13th, 2009

 

Top Down
-------------
To build an mammoth enterprise data warehouse iteratively considering all enterprise needs and then feed individual departmental data marts.

Bottom Up
------------
To build various departmental datamart from OLTPs and them conglomerate them together to form, Enterprise level data warehouse.

vikota

 Profile Answers by vikota 

• Apr 12th, 2011

 

Top-Down approach means first create the datawarehouse for entire organization then divide it into for each specific
subject are called datamarts
Bottom-Up approach means first create the data marts then by combining all data marts create the datawarehouse