Data Vault is just too slow?
You think Data Vault is a great model but you struggle with query performance?
Use Exasol as a Platform!
We have the remedy: Use our analytical database Exasol as a platform and query performance problems with Data Vault disappear.
What’s the problem with Data Vault?
The Data Vault model comes with an increased number of tables and joins. Other data warehouse platforms likely have a problem to deliver acceptable query performance with that.
Exasol solves that problem!
Exasol on the other hand is very good with joins even on many tables. We use columnar storage and we always compress data. And our database is designed to do MPP with commodity hardware.
With these attributes, combining Data Vault with Exasol delivered the best query performance for that model already using earlier versions of Exasol. And for a very reasonable price, if I may add that.
Even faster now with Exasol 7.0
Now with the release of Exasol 7.0, Data Vault performance got even better, thanks to the introduction of the HASHTYPE datatype for hash join columns and several improvements on JOIN operations.
Curious? Take action!
You want to see for yourself? Download our free Community Edition and run a test.
I bet we beat any other platform you have in place at the moment when it comes to query performance on a Data Vault model!
We’re also happy to do a PoC with your data and your queries.
As I like to say: Don’t believe it, test it 🙂
Isn’t it nice if you can make an impact with your tweets and posts? That’s what I thought today while investigating our online learning registrations.
As you may know, Exasol offers free online learning – recently also combined with free certification. We have also recently changed our course curriculum to better suit customer demands.
Together with very many IT people being in home office, that all leads to quite high numbers in registrations to our online learning platform called Exacademy: 617 in 2020 so far.
That’s many for a still quite small training & certification department like ours, and we couldn’t possibly educate that many customers with instructor-led courses.
Today, I looked at the Exacademy registrations per day:
Roughly 10 per day on average, but 74 on March 27th. What happend that day? Now I looked at my tweets from March:
Tweet analytics shows:
Looks like these 2000 impressions contributed to the unusual high number of Exacademy enrollments, which makes me quite happy 🙂
By the way, we provided 200 free certification exams so far. Get your free Exasol online training together with a free certification now: training.exasol.com
This is the second part of the mini-series Exasol on AWS. Here’s the first part.
Cloud UI is an extension to EXAoperation that makes it easy for you to
- Scale up & down
- Increase storage capacity
- Scale out by adding nodes to the cluster
Cloud UI can be reached by adding the port number 8835 to the URL of your License Server and uses the same credentials as EXAoperation.
Scale down to m5.large with Cloud UI
Depending on the load you get on your Exasol cluster, you can scale up your data nodes to more powerful EC2 instances if load is high and scale down to less expensive EC2 instances with lower user demands.
I started my little cluster with r5.large instances. Now I want to scale down to m5.large. Enter Cloud UI:
You see on the right site that scaling down to m5.large reduces both available memory and costs. I click on APPLY now and confirm the pop-up coming next with EXECUTE. The following steps the system goes through can be monitored in EXAoperation:
Notice that the database got restarted during that process.
Scale out by adding data nodes
I want to expand my present 1+0 cluster to a 2+1 cluster. First I add another active node:
As you see, this doesn’t only increase the overall avaible memory but also the compute power. Storage capacity is usually also increased when adding a node. In this particular case not, though, because I will also go from redundancy 1 to redundancy 2.
The log looks like this now:
My one node cluster did use redundancy 1, now I want to change that to redundancy 2. That step is of course not required when you started with a multi-node cluster using redundancy 2 already. See here for more details about redundancy in Exasol.
To increase redundancy, I go to the EXAstorage page of EXAoperation:
The new EC2 instance for the new data node can be renamed like this:
That makes it easier to identify the nodes, for example when associating elastic IPs to them. I do that now for n12 in the same way I did it with n11 before.
The elastic IPs of the data nodes must then be entered into the connection details of clients like DbVisualizer in this example:
After having added a new active node, that node is initially empty unless REORGANIZE operations are done. For example a REORGANIZE DATABASE:
I have a 2+0 cluster now: Mirrored segments on two active nodes but no reserve node.
Adding reserve nodes
To get a 2+1 cluster, I need to add a reserve node. Again, that’s quite easy to do with Cloud UI:
Within about 10 Minutes, the log should show something like this:
Notice that there was no database restart this time. The new node should get renamed and have a new elastic IP associated as shown before. Also that IP needs to be added to client connection details. See here if you wonder what reserve nodes are good for.
Now that I have got a 2+1 Exasol cluster running on AWS, I’m ready to demonstrate what happens if one node fails. That will be the next part of this series 🙂