EDW - Logically Integrated across multiple DBs v/s Single DB

[rohitrevo]

We have 3 divisions lets say for discussion purposes A,B and C.

B is the Core of the Warehouse since 4 years and now A wants to join in. Should we aim for a single Database to store all the Tables or should we have separate Databases for each division.

If we have a single Database, there is a hell of an effort to Allign A to B and also to change B (small as B is the base) to have commonality with A. Then there is Testing on data for multiple divisions to see the Data Integration Issues.

If we have separate databases and the have physical integration with Union views across the databases, there is less effort and less testing. There will also be a big Join effort when using these views. But it will be a nightmare to manage multiple databases and there is wastage in provisioning of space for multiple databases.

If C also takes the Database for itself approach, we will be killing the EDW.

We have a EDW. Insights required on the following:

Does Teradata have separate databases to store data for different divisions/subject areas.

What would you suggest.


Thanks

 

[avjoshi]

I would say that you are better off by integrating the data sources from all these three divisions. No doubt, it would be a major exercise. It will need a lot of time, efforts and funds to achieve successfull integration but in the end you will achieve single version of truth.

Anand