NuoDB Tour : A quick glance on NuoDB

I’m just new in my current role in my new company. One of my task is to look for a new database technologies.. that will become our platform of choice, and maybe migrate our MySQL and Oracle.

So many many new DB Technologies now, one of them in NuoDB.

To do the test drive download the software required from NuoDB. http://www.nuodb.com/product/evaluate-nuodb

To successfully run the Tour, you need to have atleast Java 7 installed.

$ curl -O http://download.nuohub.org/tgt/nuodb_tour.tar.gz
$ tar xvf nuodb_tour.tar.gz
$ cd nuodb_tour

Now let run the setup.

 
[admin@lnxnuodbtour nuodb_tour]$ sudo sh setup.sh
[sudo] password for admin:
Checking to see if THP needs to be disabled...
[always] madvise never
THP is enabled on this machine - this script will temporarily disable it
Verifying Java installation...
Verifying Docker installation...
Client:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:23:59 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:23:59 2016
 OS/Arch:      linux/amd64
Loading nuodb_eval/server:2.4.1.2 Docker image for the NuoDB hosts...
738495+1 records in
738495+1 records out
378109473 bytes (378 MB) copied, 7.55024 s, 50.1 MB/s
dbcb51e048f9: Loading layer [==================================================>] 196.9 MB/196.9 MB
4e910c38549a: Loading layer [==================================================>] 208.9 kB/208.9 kB
d43cf1f769e9: Loading layer [==================================================>] 4.608 kB/4.608 kB
a572fb20fc42: Loading layer [==================================================>] 1.024 kB/1.024 kB
a0cdcca545c8: Loading layer [==================================================>] 1.024 kB/1.024 kB
1d7642ebf6c8: Loading layer [==================================================>] 164.8 MB/164.8 MB
1f8c8b37a932: Loading layer [==================================================>] 449.5 MB/449.5 MB
5ec487afceb8: Loading layer [==================================================>] 3.584 kB/3.584 kB
d6d76b963b9a: Loading layer [==================================================>] 3.584 kB/3.584 kB
3500f8141ece: Loading layer [==================================================>] 3.584 kB/3.584 kB
a20b6a8acfd4: Loading layer [==================================================>] 1.024 kB/1.024 kB
Setup is complete. You can now run 'deploy.sh' to start nuodb containers.
[admin@lnxnuodbtour nuodb_tour]$

Now our Docker container is ready.

screen-shot-2016-12-22-at-8-53-06-pm

Now let deploy our NuoDB.

 
[admin@lnxnuodbtour nuodb_tour]$ sudo ./deploy.sh --user nuodb_admin --password nuodb
Starting container nuodb1
2016-12-21 01:32:31,887 CRIT Supervisor running as root (no user in config file)
2016-12-21 01:32:31,890 INFO supervisord started with pid 10
2016-12-21 01:32:32,895 INFO spawned: 'nuorestsvc' with pid 13
2016-12-21 01:32:32,902 INFO spawned: 'nuoagent' with pid 14
2016-12-21 01:32:33,908 INFO success: nuorestsvc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-12-21 01:32:33,908 INFO success: nuoagent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-12-21 01:32:34,065 INFO exited: nuoagent (exit status 0; expected)
Starting container nuodb2
2016-12-21 01:32:37,928 CRIT Supervisor running as root (no user in config file)
2016-12-21 01:32:37,931 INFO supervisord started with pid 10
2016-12-21 01:32:38,193 INFO exited: nuorestsvc (exit status 0; expected)
2016-12-21 01:32:38,933 INFO spawned: 'nuoagent' with pid 13
2016-12-21 01:32:39,954 INFO success: nuoagent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-12-21 01:32:40,134 INFO exited: nuoagent (exit status 0; expected)
Starting container nuodb3
2016-12-21 01:32:41,861 CRIT Supervisor running as root (no user in config file)
2016-12-21 01:32:41,864 INFO supervisord started with pid 10
2016-12-21 01:32:42,868 INFO spawned: 'nuoagent' with pid 13
2016-12-21 01:32:43,871 INFO success: nuoagent entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2016-12-21 01:32:44,011 INFO exited: nuoagent (exit status 0; expected)
next>
create domain administrator user nuodb_admin password nuodb
next>

Provisioning is done. Please go back to the doc for next steps.
You can manage your NuoDB Domain by running:

   ./nuodbmgr --user nuodb_admin --password nuodb

[admin@lnxnuodbtour nuodb_tour]$

Now lets verify if our broker is running.

 
[admin@lnxnuodbtour nuodb_tour]$ sudo ./nuodbmgr --user nuodb_admin --password nuodb
[sudo] password for admin:
NuoDB host version: 2.4.1-2: Professional Edition
nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

nuodb [domain] >

screen-shot-2016-12-22-at-8-53-19-pm

Now lets create a Single Domain database.

[admin@lnxnuodbtour nuodb_tour]$  sudo ./nuodbmgr --user nuodb_admin --password nuodb
[sudo] password for admin:
NuoDB host version: 2.4.1-2: Professional Edition
nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

nuodb [domain] > create database
Database Name: demodb
DBA User: dba
DBA Password: dba
Template Name (Single Host, Minimally Redundant, Multi Host, Geo-distributed): Single Host
Template Variables (optional):
Database Options (optional): mem 128m
Timeout (ms/s/m/h/d/w) (optional):
Template Variable HOST (default: localhost): nuodb1
Database Options for TEs (optional):
Tag Constraints for TEs (optional):
Database Options for SMs (optional):
Tag Constraints for SMs (optional):
nuodb [domain] >  show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Single Host] MET, processes [1 TE, 1 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 578 ] [ nodeId = 2 ] RUNNING

nuodb [domain] >

As you can see above TE and SM only started on nuodb1 (node1), since its only a Single Host.
screen-shot-2016-12-22-at-8-53-33-pm

Let’s create some tables.

nuodbadmin@lnxnuodbtour:~/nuodb_tour$ sudo ./nuosql demodb --user dba --password dba
SQL> 

SQL> show tables;

    No tables found in schema USER


SQL> show schema;

    Current schema is USER


SQL>


SQL> create table users (id bigint generated always as identity primary key, name string not null, gender char(1) check (gender in ('M','F')));
SQL> insert into users (name, gender) values ('Ada Lovelace','F'), ('Alan Turing', 'M'), ('Donald Knuth', 'M');
SQL> select * from users;

 ID      NAME     GENDER
 --- ------------ -------

  1  Ada Lovelace    F
  2  Alan Turing     M
  3  Donald Knuth    M

SQL> show table users

    Tables named USERS

    Found table USERS in schema USER

        Fields:
            ID bigint
                Nullable: No
                Generator: USERS$IDENTITY_SEQUENCE    Generated Always
            NAME string
                Nullable: No
            GENDER char(1)
                Constraint: GENDER in ('M','F')
        Primary Index: USERS..PRIMARY_KEY on field: ID

SQL>

Above example is just like the same with other database… what i like is when you add more nodes to the configuration. it’s very easy unlike oracle or mysql.
screen-shot-2016-12-22-at-8-53-54-pm

Now Let update our database to a Minimimally Redundant.
unlike other database, in NuoDB it’s like altering a table.

nuodb [domain] > update database
Database Name: demodb
Template Name (Single Host, Minimally Redundant, Multi Host, Geo-distributed): Minimally Redundant
Template Variables (optional):
Database Options (optional): mem 128m
Template Variable REGION (default: DEFAULT_REGION):
Database Options for TEs (optional):
Tag Constraints for TEs (optional):
Database Options for SMs (optional):
Tag Constraints for SMs (optional):
nuodb [domain] >

Now lets check ..

nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED
>>> as you can see below, it says UNMET since the broker still in the process of starting the TE and SM  <<<<<<
Database: demodb, template [Minimally Redundant] UNMET, processes [1 TE, 1 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 578 ] [ nodeId = 2 ] RUNNING

after a couple of seconds, 2 TE and 2 SM running.
nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 578 ] [ nodeId = 2 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] >

Part of the tour, the included sample program to simulate a load to the database. while the program is running we will try to kill some node and see what happens.

Execute below to populate our database.
./nuosql demodb --user dba --password dba --schema hockey  create-db.log 2>&1
./nuosql demodb --user dba --password dba --schema hockey  players.log 2>&1
./nuosql demodb --user dba --password dba --schema hockey  scoring.log 2>&1
./nuosql demodb --user dba --password dba --schema hockey  teams.log 2>&1

SQL> show schema

    Current schema is USER


SQL> show schemas;

    Found 3 schemas
        HOCKEY
        SYSTEM
        USER (current)


SQL>


SQL> use hockey
SQL> SHOW TABLES;

    Tables in schema HOCKEY
        HOCKEY
        PLAYERS
        SCORING
        TEAMS
        VW_PLAYER_STATS is a view


SQL> SHOW TABLE players;

    Tables named PLAYERS

    Found table PLAYERS in schema HOCKEY

        Fields:
            PLAYERID varchar(10)
                Nullable: No
            FIRSTNAME varchar(32)
            LASTNAME varchar(32)
            HEIGHT integer
            WEIGHT integer
            FIRSTNHL integer
                Nullable: No
                Default: 0
            LASTNHL integer
                Nullable: No
                Default: 0
            POSITION varchar(8)
            BIRTHYEAR integer
            BIRTHMON integer
            BIRTHDAY integer
            BIRTHCOUNTRY varchar(32)
            BIRTHSTATE varchar(32)
            BIRTHCITY varchar(32)
        Primary Index: PLAYERS..PRIMARY_KEY on field: PLAYERID

SQL> SELECT firstname,lastname FROM players limit 10;

 FIRSTNAME   LASTNAME
 ---------- ----------

  Antti     Aalto
  Bruce     Abbey
  George    Abbott
  Reg       Abbott
  Justin    Abdelkader
  Clarence  Abel
  Gerry     Abel
  Sid       Abel
  Dennis    Abgrall
  Ramzi     Abid

SQL>

Now, since our database has some data, let’s run program that will do the query on our database.

nuodbadmin@lnxnuodbtour:~/nuodb_tour$ java -cp ./jdbc:./jdbc/nuodbjdbc.jar Client1 &
[1] 7354
nuodbadmin@lnxnuodbtour:~/nuodb_tour$ java -cp ./jdbc:./jdbc/nuodbjdbc.jar Client2 &
[2] 7355
nuodbadmin@lnxnuodbtour:~/nuodb_tour$ java -cp ./jdbc:./jdbc/nuodbjdbc.jar Client3 &
[3] 7406
nuodbadmin@lnxnuodbtour:~/nuodb_tour$
nuodbadmin@lnxnuodbtour:~/nuodb_tour$

On other session, let do the query.

sudo ./nuosql demodb --user dba --password dba
SQL> SELECT sqlstring, nodeid FROM system.connections;

                                       SQLSTRING                                        NODEID
 -------------------------------------------------------------------------------------- -------

 SELECT sqlstring, nodeid FROM system.connections;                                         4
 select id, number, firstname, lastname from hockey, players                               4
 select playerid from scoring union all select playerid from players where weight > 260    4
 select playerid from scoring union all select playerid from players where weight > 260    2

SQL> SELECT sqlstring, nodeid FROM system.connections;

                                       SQLSTRING                                        NODEID
 -------------------------------------------------------------------------------------- -------

 SELECT sqlstring, nodeid FROM system.connections;                                         4
 select playerid from scoring union all select playerid from players where weight > 260    4
                                                                                           2
                                                                                           2

SQL>

As you can see above, 2 TE is serving the application.
Now let’s kill 1 our our TE.

sudo ./nuodbmgr --user nuodb_admin --password nuodb

nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 578 ] [ nodeId = 2 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] > shutdown process
Host: 172.17.0.2
Process ID: 578
Shutdown gracefully (optional):
Shutdown even if database would become non-durable (optional):
Timeout (ms/s/m/h/d/w) (optional):
Remote process shutdown timeout (ms/s/m/h/d/w) (optional):
Process shutdown cleanly
nuodb [domain] >  show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] UNMET, processes [1 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] >  show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 5289 ] [ nodeId = 5 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] >

On our separate session, let run again the query.

SQL> !!
sELECT sqlstring, nodeid FROM system.connections;

                                       SQLSTRING                                        NODEID
 -------------------------------------------------------------------------------------- -------

 sELECT sqlstring, nodeid FROM system.connections;                                         4
 select playerid from scoring union all select playerid from players where weight > 260    4
 select id, number, firstname, lastname from hockey, players                               5
 select playerid, teamid, assists from scoring                                             5

SQL>

TO SATISFY THE MINIMALLY REDUNDANT CONFIGURATION, NUODB AUTOMATICALLY START A NEW TE, WITHOUT DBA INTERVENTION.

Now lets kill 1 our SM.

nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 562 ] [ nodeId = 1 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 5289 ] [ nodeId = 5 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] >

nuodb [domain] > shutdown process
Host: 172.17.0.2
Process ID: 562
Shutdown gracefully (optional):
Shutdown even if database would become non-durable (optional):
Timeout (ms/s/m/h/d/w) (optional):
Remote process shutdown timeout (ms/s/m/h/d/w) (optional):
Process shutdown cleanly
nuodb [domain] >
nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 19807 ] [ nodeId = 6 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 5289 ] [ nodeId = 5 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] >

as you can see, a new SM is started on the same node.

as you can see below, our test application is still running and connected to both TE.

SQL> !!
sELECT sqlstring, nodeid FROM system.connections;

                                       SQLSTRING                                        NODEID
 -------------------------------------------------------------------------------------- -------

 sELECT sqlstring, nodeid FROM system.connections;                                         4
 select playerid, teamid, assists from scoring                                             4
 select id, number, firstname, lastname from hockey, players                               5
 select playerid from scoring union all select playerid from players where weight > 260    5

SQL>

Now let’s update our configuration to Multi Host and see what happens.

nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Minimally Redundant] MET, processes [2 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 19807 ] [ nodeId = 6 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 5289 ] [ nodeId = 5 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain] > update database
Database Name: demodb
Template Name (Single Host, Minimally Redundant, Multi Host, Geo-distributed): Multi Host
Template Variables (optional):
Database Options (optional): mem 128m
Template Variable REGION (default: DEFAULT_REGION):
Database Options for TEs (optional):
Tag Constraints for TEs (optional):
Database Options for SMs (optional):
Tag Constraints for SMs (optional):
nuodb [domain] > show domain summary;

Hosts:
[broker] * nuodb1/172.17.0.2:48004 (DEFAULT_REGION) CONNECTED
[broker] nuodb2/172.17.0.3:48007 (DEFAULT_REGION) CONNECTED
[broker] nuodb3/172.17.0.4:48010 (DEFAULT_REGION) CONNECTED

Database: demodb, template [Multi Host] MET, processes [3 TE, 2 SM], ACTIVE
[SM] nuodb1/172.17.0.2:48005 (DEFAULT_REGION) [ pid = 19807 ] [ nodeId = 6 ] RUNNING
[TE] nuodb1/172.17.0.2:48006 (DEFAULT_REGION) [ pid = 5289 ] [ nodeId = 5 ] RUNNING
[SM] nuodb2/172.17.0.3:48008 (DEFAULT_REGION) [ pid = 124 ] [ nodeId = 3 ] RUNNING
[TE] nuodb2/172.17.0.3:48009 (DEFAULT_REGION) [ pid = 156 ] [ nodeId = 7 ] RUNNING
[TE] nuodb3/172.17.0.4:48011 (DEFAULT_REGION) [ pid = 125 ] [ nodeId = 4 ] RUNNING

nuodb [domain]

as you can see a new TE had been started.

Now lets run our query if the new TE is serving our application.

SQL> !!
sELECT sqlstring, nodeid FROM system.connections;

                          SQLSTRING                          NODEID
 ----------------------------------------------------------- -------

 sELECT sqlstring, nodeid FROM system.connections;              4
 select playerid, teamid, assists from scoring                  7
 select id, number, firstname, lastname from hockey, players    5

SQL>

Now the tour is done. though i want to test more but the tour has some limitation. once i get my trial/poc i will update more…

NuoDB will make DBA’s like more easy and maybe reduce the headcount of DBA’s per company in the Future.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s