ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

Quest: All content tagged as Quest in NoSQL databases and polyglot persistence

NoSQL databases, Quest Software, and Toad for Cloud

I wrote a couple of times about Quest Software’s Toad for Cloud[1], the free Eclipse tool that allows connecting to NoSQL databases and working with data in a tabular, SQLish format. But having in mind Quest’s business, there was something bugging me about Quest’s initiative: why would they make these tools? Even more, why would they make them available for free?

I think I got an answer to these questions. One area of expertise of Quest Software is represented by relational databases management tools. If offering these free tools would make it easy to see all data as tabular once again, moreover would make it easy to move it back to relational database, then Quest Software’s database management tools will continue to sell well and also enter the NoSQL databases market.

This is somehow similar to what Cloudera is doing for Hadoop: creating an ecosystem that enables everyone to important data into Hadoop. As long as more companies are using Hadoop, the more chances are Cloudera’s business will prosper.

Original title and link: NoSQL databases, Quest Software, and Toad for Cloud (NoSQL databases © myNoSQL)


Hadoop Spreading through Cloudera Parternships

Cloudera in its attempt to Hadoopize the world goes on partnership spree:

Many of you may have read about some of the recent announcements of partnerships between Cloudera and some of the leading data management software companies like Teradata, Netezza, Greenplum (EMC), Quest and Aster Data. We established these partnerships because Hadoop is increasingly serving as an open platform that many different applications and complimentary technologies work with. Our goal is to to make this as easy and as standardized as possible.

Checking the ☞ press release section turns out the following parnerships:

  • Membase
  • Talend
  • Quest
  • Pentaho
  • NTT Data
  • Aster Data
  • EMC Greenplum
  • Teradata
  • Netezza

Quite a few companies from the non-relational market.

Original title and link: Hadoop Spreading through Cloudera Parternships (NoSQL databases © myNoSQL)

via: http://www.cloudera.com/blog/2010/10/cdh3-beta-3-now-available/


Riptano and Quest Partnership for Cassandra

When talking if a common query language for NoSQL databases would make sense, I’ve mentioned an interesting initiative from Quest Software, ☞ Toad for Cloud, that, through an indirection layer, would provide a SQL interface to NoSQL databases. There are still lots of open technical questions about such a tool, but I hope to clarify them shortly.

Today, Quest is releasing a new version of Toad for Cloud which features support for Cassandra, adding it to a list of already supported NoSQL databases like HBase, Amazon SimpleDB, and Microsoft Azure Table Service.

But that’s not all, as Quest Software and Riptano are also announcing a technology alliance with the goal of promoting Cassandra inside the enterprise market. Together they will conduct researches to determine the needs for specialized Cassandra tools (e.g. monitoring, diagnosis, ETL, et.c) that would make Cassandra appealing to this market.


I’ve been briefed about this announcement, but in case you need an official/PR announcement you can find one ☞ here

Original title and link for this post: Riptano and Quest Partnership for Cassandra (published on the NoSQL blog: myNoSQL)