Skip to main content

Toad for Cloud Databases

Looking for a free(!) tool to connect to your Cloud databases? One of the tools I’ve been trying is Toad for Cloud Databases, a free SQL-based tool with the familiar look and feel of Toad, which enables users to use SQL(yes indeed SQL) with a set of  non-relational databases, including Hadoop (Hbase & Hive), Cassandra, MongoDB, SimpleDB, and Azure Table Services.

How does it work?

There are two key components to Toad for Cloud Databases:

  • Toad client: Use it to access Cloud/NoSQL databases via SQL statements.
  • Data Hub: It translates SQL statements submitted through the Toad client into a language understood by the Cloud database, and returns results in the familiar tabular row and column format.
Installation

You can download it from the following location(you’ll have to register first): http://toadworld.com/Freeware/ToadforCloudDatabasesFreeware/tabid/842/Default.aspx

Run the installer after downloading has completed.

Get started
  • Start the Toad for Cloud Databases client. Once the client is loaded you’ll see the Data Explorer on the left.

image

  • Right click on the Embedded Data Hub and choose Map Data Source…

image

  • The Map Data Source wizard is loaded. Specify a Data source name and choose the appropriate Data source type(we’ll choose Azure Table Services).

image

  • Specify the credentials to connect to your data source and click OK to complete this step.

image

  • The data source is added to the Tree view.

image

  • However before we can start doing something, we have to create a mapping first. Right click on the Mappable Objects and choose Map Multiple Tables…

image

  • The Map Tables screen is loaded. Select the Table you want to map and click OK.

image

  • The tool will create a Table for us and map all the found columns as can be seen in the Data Explorer Tree view.

image

  • Now we can right-click on the created table and start writing SQL by choosing Open SQL Editor.

image

  • A SQL Editor is opened and you can write and execute SQL statements.

image

  • That’s it!
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more