In a perfect world, you should like to have a separate server for
production and test systems. If that is not currently feasible, then
I would recommend creating a separate instance of DB2 for your test
databases. It can be a single server and single software installation.
A separate instance is a separate running copy of the DBMS server, listening
on a separate port for connections, and managing its own databases.
This will allow you to stop and start the test and production systems
separately, and also to test changes in the database manager configuration
on the test system isolated from your production databases. It will also
allow you to enforce different security policies in your test and production
systems-- for instance, where I work, all of our DBAs have SYSADM authority
on test instances, but only the DBAs with primary responsibility for DB2
administration have SYSADM on the production instances. You also can
do things like give DBAs SYSCTRL on production systems instead of SYSADM
if the data is sensitive and should be kept confidential from system
administrators.
Hope that helps,
Joseph
Jep <do**********@jepweb.dk> writes:
We plan for 1 (big) server to host both a production and test database
for a system, and some other small db's. Databases to be put on a SAN.
But I don't understand the topics concerning installation and
administration. What can I do and what can't I do, when multiple
databases reside on the same server.
Can there be a setup, so that the test database can be stopped/started
without interupting the production database ??
There must be some Administrative topics I ought to know about??
/Jep