Using CUBRID Management Tools
Running SQL with CUBRID Web Manager
Because CUBRID 2008 R4.3 or higher version includes Web Manager into the installation package, you can use the Web Manager instantly after the installation of CUBRID DBMS.
- Start CUBRID Service. Web Manager works normally only when CUBRID Manager server is started. For more information, see Starting and Stopping CUBRID Manager Server.
C:CUBRID>cubrid service start
++ cubrid service is running.
- Access to https://localhost:8282 which is written on the address bar. The default TCP port is 8282 (HTTPS/SSL) and it is possible to change by editing the cm_httpd.conf file at CUBRID/conf/. Note that the header of address is not http, but https.
- First, log in to the host. To access to the host, you should perform the CUBRID Manager server user (=the host user)'s authentication primarily. The default user ID/password is admin/admin.
- Secondary, connect to the DB server. In the tree on the left, you can see the list of databases which have been generated within the corresponding host. Click the DB name that you want to access and perform the DB user authentication (default ID/password: dba/pressing enter key)
- Run the SQL on the access DB and confirm the result. On the left side, the list of connected databases are displayed. You can edit, run, and find the result on the SQL tab.
For more information, see http://www.cubrid.org/wiki_tools/entry/cubrid-web-manager-manual.
Running SQL with CUBRID Manager Client
CUBRID Manager is the client tool that you should download and run. It is a Java application which requires JRE or JDK 1.6 or higher.
- Download and install the latest CUBRID Manager file. CUBRID Manager is compatible with CUBRID DB engine 2008 R2.2 or higher version. It is recommended to upgrade to the latest version periodically; it supports the auto-update feature.
(CUBRID ftp: http://ftp.cubrid.org/CUBRID_Tools/CUBRID_Manager/.
- Start CUBRID service on the server. CUBRID Manager server should be started for CUBRID Manager client to access to DB. For more information, see Starting and Stopping CUBRID Manager Server.
C:CUBRID>cubrid service start
++ cubrid service is running.
- After the installation of CUBRID Manager, register host information on the [File > Add Host] menu. To register the host, you should enter host address, connection port (default: 8001), and CUBRID Manager user name/password and install the JDBC driver of the same version with DB engine (supporting auto-driver-search/auto-update).
- Choose the host on the left tress and perform the CUBRID Manager user (=host user) authentication. The default ID/password is admin/admin.
- Run SQL on the access DB and confirm the result. The host, DB and table list are displayed on the left side, and the query editor and the result window is shown on the right side. You can reuse the SQLs which have been succeeded with [SQL History] tab and compare the multiple results of several DBs as adding the DBs for the comparison of the result with [Multiple Query] tab.
For more information, see http://www.cubrid.org/wiki_tools/entry/cubrid-manager-manual.
Running SQL with CUBRID Query Browser
CUBRID Query Browser (hereafter CQB) is the development tool only for SQL execution, light-weight version of CUBRID Manager (hereafter CM). The differences with CM are as follows:
- CQB can access directly to DB via JDBC, without going through CM server.
- As a result, DB/broker operating and monitoring features are not supported.
- As a result, CQB only logs in DB user and CM user login is unnecessary.
- CUBRID Manager server running on the server side is unnecessary.
CQB client tool also needs to be downloaded separately. It is executed on a Java applications which require JRE or JDK 1.6 version or later.
- Install the latest CQB file after download. It is compatible with any versions of the engine if you just add the same version's JDBC driver with the DB server. It is recommended to upgrade to the latest version periodically because it supports the auto-update feature.
(CUBRID ftp: http://ftp.cubrid.org/CUBRID_Tools/CUBRID_Query_Browser/.
- Register DB access information on the [File > New Connection] menu after installing CQB. In this case, broker address, broker access port (default: 33,000), DB user, and password should be entered and the JDBC driver which has the same version with DB server should be installed (supporting auto-driver-search/auto-update).
- Try to access as choosing DB. In this case, perform DB authentication (default: dba/pressing enter key).
- Run SQL on the access DB and confirm the result. The lists of Host, DB, and table are displayed on the left side, and the query editor/result window are shown on the right side. You can reuse the SQLs which have been succeeded with [SQL History] tab and compare the multiple results of several DBs as adding the DBs for the comparison of the result with [Multiple Query] tab.
For more information, see http://www.cubrid.org/wiki_tools/entry/cubrid-query-browser-manual.
Migrating schema/data with CUBRID Migration Toolkit
CUBRID Migration Toolkit is a tool to migrate the data and the schema from the source DB (MySQL, Oracle, and CUBRID) to the target DB (CUBRID). It is also Java applications which require JRE or JDK 1.6 or later. You should download separately.
(CUBRID ftp: http://ftp.cubrid.org/CUBRID_Tools/CUBRID_Migration_Toolkit/)
It is useful in cases of swiching a DB to CUBRID to migrating to other hardware, migrating some schema and data from the operating DB, upgrading CUBRID version, and running the batch jobs. The main features are as follows:
- Supports the tools/some schema and data migration
- Available to migrate only the desired data as running several SQLs
- Executable without suspending of operation as supporting online migration through JDBC
- Available offline migration with CSV, SQL, CUBRID loaddb format data
- Available to run directly on the target server as extracting the run-script of migration
- Shorten the batch job time as reusing the migration run-script.
For more information, see http://www.cubrid.org/wiki_tools/entry/cubrid-migration-toolkit-manual.