| There are many nice inbuilt DB2 GUI tools available. | | | | You can add instances and drop instances by using |
| Some people use external tools like quest central, | | | | control center. Pretty much an instance can have one |
| DBArtisan etc to do their day to day jobs. But it is not | | | | or more databases. So each of the database has to |
| necessary for some people as they prefer inbuilt tools | | | | be added separately once the instance is added. You |
| like control center and replication center. Control center | | | | can connect to a database and play with all the |
| is decent but it is slow at times and not so user friendly | | | | objects inside the database. You can create/drop |
| as some other third party tools. | | | | tablespaces, bufferpools, tables, indexes, aliases, views |
| Control center is one of the important ones here. It can | | | | and other objects there. So pretty much all the object |
| be invoked by issuing a DB2CC on the command | | | | level tasks can be done using control center. Some |
| window or starting it from the windows menu. After it | | | | people prefer to use this GUI tool rather than going on |
| loads you will see list of servers, instances and | | | | to the unix shell and typing the command. |
| databases on the left margin. You can pretty much | | | | Another important thing to be discussed here is the |
| login to any of these databases by giving the | | | | toolbar. Toolbar in the control center acts as a |
| appropriate user name and password information. | | | | navigating menu to other important built in facilities. |
| These databases are to be cataloged to begin with. | | | | Replication center, task center, data warehouse center, |
| Host name and port number are needed to catalog a | | | | development center and all can be invoked from the |
| database server and the database. | | | | toolbar. |