Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Creating a Database

Use the procedures below to create either an Enterprise Mode or Eon Mode database with admintools. To create a database with an in-browser wizard in Management Console, see Create an Empty Database Using MC.

Enterprise Mode Versus Eon Mode

You can create a database in Enterprise Mode or Eon Mode. The two types of modes differ in their architecture, deployment, and scalability:
  • Enterprise Mode database architecture distributes data across local nodes, and works on-premise or in the cloud. Consider creating the database in this mode on a cluster of predetermined size, which is good for running large queries quickly. Because it persistently stores its data locally, you do not need to have access to shared storage on Amazon S3 to use an Enterprise Mode database. Enterprise Mode Concepts includes an overview of how data store works on a database running in Enterprise Mode. (If you prefer to create an Enterprise Mode database on-premise, first see Installing Vertica.)
  • Eon Mode databases' architecture leverages the flexibility of EC2 instances and the persistence of Amazon S3. Eon Mode databases are ideal when you want to frequently scale up your cluster in order to run many short, concurrent queries. Because an Eon Mode database stores its data in a persistent location outside of its local nodes, you can rapidly adjust the size of your cluster without interrupting ongoing workloads when you do so. (See Using Eon Mode for more about Eon Mode database concepts.)

Create an Enterprise Mode Database

  1. On the Configuration Menu, click Create Database. Click OK.
  2. Select Enterprise Mode as your database mode.
  3. Enter the name of the database and an optional comment. Click OK.
  4. Enter a password. See Creating a Database Name and Password for rules.
    If you do not enter a password, you are prompted to confirm: Yes to enter a superuser password, No to create a database without one.
    If you do not enter a password at this point, superuser password is set to empty. Unless the database is for evaluation or academic purposes, Vertica strongly recommends that you enter a superuser password.
  5. If you entered a password, enter the password again.
  6. Select the hosts to include in the database. The hosts in this list are the ones that were specified at installation time (install_vertica -s).
    Database Hosts
  7. Specify the directories in which to store the catalog and data files.
    Database data directories
    Catalog and data paths must contain only alphanumeric characters and cannot have leading space characters. Failure to comply with these restrictions could result in database creation failure.
    Do not use a shared directory for more than one node. Data and catalog directories must be distinct for each node. Multiple nodes must not be allowed to write to the same data or catalog directory.
  8. Check the current database definition for correctness. Click Yes to proceed.
    CurrentDatabaseDefinition
  9. A message indicates that you have successfully created a database. Click OK.

Create an Eon Mode Database

  1. On the Configuration Menu, click Create Database. Click OK.
  2. Select Eon Mode as your database mode.
  3. Enter the name of the database and an optional comment. Click OK.
  4. Enter a password. See Creating a Database Name and Password for rules.
    AWS only: If you do not enter a password, you are prompted to confirm: Yes to enter a superuser password, No to create a database without one.
    If you do not enter a password at this point, superuser password is set to empty. Unless the database is for evaluation or academic purposes, Vertica strongly recommends that you enter a superuser password.
  5. If you entered a password, enter the password again.
  6. Select the hosts to include in the database. The hosts in this list are those specified at installation time (install_vertica -s).
  7. Specify the directories in which to store the catalog and depot, depot size, communal storage location, and number of shards.
    • Depot Size:  Use an integer followed by %, K, G, or T. Default is 60% of the disk total disk space of the filesystem storing the depot.
    • Communal Storage: Use an existing Amazon S3 bucket in the same region as your instances. Specify a new subfolder name, which Vertica will dynamically create within the existing S3 bucket. For example, s3://existingbucket/newstorage1. You can create a new subfolder within existing ones, but database creation will roll back if you do not specify any new subfolder name.
    • Number of Shards: Use a whole number. The default is equal to the number of nodes. For optimal performance, the number of shards should be no greater than 2x the number of nodes. When the number of nodes is greater than the number of shards (with ETS), the throughput of dashboard queries improves. When the number of shards exceeds the number of nodes, you can expand the cluster in the future to improve the performance of long analytic queries.
    Catalog and depot paths must contain only alphanumeric characters and cannot have leading space characters. Failure to comply with these restrictions could result in database creation failure.
  8. Check the current database definition for correctness. Click Yes to proceed.
  9. A message indicates that you successfully created a database. Click OK.

Comments

Popular posts from this blog

PostgreSQL pgBadger

PostgreSQL Pgbadger Installation On Linux

How to configure Replication Manager (repmgr) ?

Migrating From Oracle to PostgreSQL using ora2pg open source tools

7 Steps to configure BDR replication in postgresql