The differences I look at when determining multiple database engines vs combined ones are:
1. Memory foot print is greater with multiple databases. 2. Database caching can be greater with multiple databases (assuming you have the real memory) 3. High availability vs highly dynamic databases. (Can't just take down high availability databases easily. Changes that need a database cycle may need to be planned far in advance. VS Dynamic databases may require database outages on a more frequent, near immediate basis. ) 4. Application requirements. Can the applications easily access all the data needed without something like DataJoiner involved? 5. What are the test database requirements? 6. How to stage new releases of the database and/or applications in the future. 7. Management of multiple databases is more complex. 8. Security of multiple databases can be much tighter.
I'm in the small/medium mainframe side, so I'm not speaking from the high power end of the house.
Tom Duerbusch THD Consulting
David Boyes wrote:
do i setup 1 db2 per linux instance
or more than 1 db2 on a linux instance
police db2 on linux1 finance db2 on linux2 payroll db2 on linux3
or all the above on linux1??
All of the above are legitimate. I favor separate Linux instances for isolation purposes, but there is no technical reason that they cannot all be in one big instance if that's more comfortable for you.
