Evaluation Guide : 3. Stage 1--Define and Create the Test Environment : Using VectorH
 
Share this page                  
Using VectorH
After completing the tasks in Installation, you should have a running VectorH installation, know how to stop and start the instance, create a database, connect with the terminal monitor, setup client connectivity, and install Actian Director.
There should also be a database called pocdb running under instance VH, a user actian with password actian that is ready to use for testing. If you require a different setup, however, additional details are given in this section. It may be useful to read this section in conjunction with the sample scripts provided for Running the Performance Test Kit.
Stopping and Starting the Instance
Start the instance with the ingstart command. Stop the instance with the ingstop command.
Creating and Removing Databases
To create a database, use the createdb command. The basic syntax is:
createdb <database name>
You can run multiple databases under the one instance, but each database will take the full resource allocation as described in Configuring Database Resources. If running multiple databases, reduce the allocated resources given to each database. This can be done by lowering the resources allocated in the shared configuration file, or by giving each database its own configuration file (see the System Administrator Guide).
If running under YARN, the instance should have only one database. Running multiple databases under YARN is possible, but requires experience in configuring both YARN and VectorH.
To remove a database, use the destroydb command:
destroydb <database name>
Note:  By default, destroydb will destroy the data without asking for confirmation (presuming you are the owner of the database)!
Stopping and Starting a Database
An x100 process for a VectorH database will start upon the first user connection and will remain running until either the x100 process is stopped or the instance is stopped.
If performing a benchmark, you may want to connect to the database at least once before running a test to ensure that x100 startup times are not included in the query time, giving a false impression of “cold-cache” query times. The query select * from <table> where 1=2 can be used to ensure full start up without caching any data.
To stop a running x100 process for a database, either stop the instance with ingstop or connect to the database and issue the command call vectorwise(terminate).
Users, Groups, Profiles, Permissions
If you need to set up additional users, groups, user profiles, and configure security settings, consult the Security Guide, SQL Language Guide, and Actian Director User Guide.