June 14, 2007 at 9:59 am
Our data warehouse consists of three databases. We have some tables and processes that are used across all three databases. Where should we keep these common tables and processes?
This is a new environment for me. In past roles, each database was a whole, exclusive entity in itself. In my current role, we have, for instance, meta data tables and stored procs that are used across all three databases but it is unclear to my what the best practice in terms of where to keep these. Should it be a separate database for the common elements?
Thanks.
June 15, 2007 at 9:26 am
If you have three databases, which database do you put the common tables and processes?
I would use a new database for comman tables and processes, if it is meta data tables, definitely it should have its own database.
June 15, 2007 at 9:53 am
Perhaps I should have clarified a bit more. Really the common tables and proc were isolated but now we are finding opportunities to make the meta data tables and the procs more generic, which means that effectively meta data and procs for each database have started to creep into the other databases such that a scattered, confusing distribution is growing.
I had guessed that a separate database was an appropriate solution. Since I lack experience with this problem/environment I was seeking to tap into those that have such experience.
Thanks much.
>>If you have three databases, which database do you put the common tables and processes?
>>I would use a new database for comman tables and processes, if it is meta data tables, definitely it should have its own database.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply