Google cloud glitch forces SQL backups

cloudGoogle’s Cloud SQL service was hit by rather a nasty glitch over the weekend and more than seven percent of clients using the service’s first-generation code were not backing up properly.

Google announced it was “forcing” backups “as short-term mitigation” and was expected to issue a patch today.

The news comes just as Google is announcing the release of its new Cloud Spanner product.

For those who came in late, Cloud Spanner is a horizontally-scalable and strongly consistent relational database, combining the company’s two other DBaaS solutions, NoSQL and RDBMS, offering a wider range of services including ACID transactions and SQL semantics. It’s targeting AWS’s RDS and Microsoft’s SQL Database in the public cloud.

Product manager, Dominic Preuss wrote in his bog that Google had carefully designed Cloud Spanner to meet customer requirements for enterprise databases — including ANSI 2011 SQL support, ACID transactions, 99.999% availability and strong consistency — without compromising latency”.

“As a combined software/hardware solution that includes atomic clocks and GPS receivers across Google’s global network, Cloud Spanner also offers additional accuracy, reliability and performance in the form of a fully-managed cloud database service.”

While traditional databases guarantee transactional consistency, while NoSQL databases offer horizontal scaling and data distribution. The aim for Cloud Spanner is to offer cloud developers both capabilities.

Cloud Spanner is available now via a trio of data integration partners, Alooma, Informatica and Xplenty.

“Cloud Spanner is one of those cloud-based technologies for which businesses have been waiting: With its horizontal scalability and ACID compliance, it’s ideal for those who seek the lower TCO of a fully managed cloud-based service without sacrificing the features of a legacy, on-premises database,” Xplenty said.

Google is offering a free trial of Cloud Spanner so companies can see how it would work for them.