Traditional SQL DaaS or NewSQL

September 23rd, 2011

Mike Hogan uses the following to suggest a move to NewSQL: Lack of Business Visibility Cripples Traditional SQL DaaS, Drives NewSQL.

the shift to a database as a service (DaaS) severely reduces the DBAs visibility into the business, thus limiting the ability to hand tune the database to the requirements of the application and the database. The solution is a cloud database that eliminates the hand-tuning of the database, thereby enabling the DBA to be equally effective even with limited visibility into the business and application needs

I agree with the problem positioning, but feel strongly that NewSQL is not a requirement to address the problem here, you can equally work a little services layer and put all the control into the hands of the user, essentially replacing (a lot of) the DBA tasks with automation and APIs.

What NewSQL gives you though, and we see that with Xeround and supposedly also ScaleDB, is the elasticity and transparent sharding that’s difficult to achieve with the more traditional Oracle, Sybase or SQL Server databases that are still often required in the enterprise space.

Related posts:

  1. Cloud DaaS Managed Service Fuels NewSQL Market
  2. The Importance of IMDB for SAP
  3. How will the DB incumbents respond to NoSQL and NewSQL?
  4. HP buying Stratavia
  5. Cloud Databases

3 Responses to “Traditional SQL DaaS or NewSQL”

  1. Dolley Says:

    I’m impressed by your writing. Are you a professional or just very kownlegdaeble?

  2. onoithjmon Says:

    SxSwl2 vzyycqvxhfus

  3. xaiwytieb Says:

    uqX9uZ sxikesjzqwkt

Leave a Reply

Comments will be sent to the moderation queue.

Maximum 5 links per comment. Do not use BBCode.