rdbms: All content tagged as rdbms in NoSQL databases and polyglot persistence
Today’s database landscape isn’t just static. It’s positively retro. Remember 2004? Facebook had just launched, the iPad wasn’t even a twinkle in Steve Jobs’ eye, and Gartner’s database market share report put IBM (34.1%), Oracle (33.7%), and Microsoft (20%) in the top spots. In our survey, Microsoft, Oracle, and IBM still hold the top spots; we do add MySQL, but that’s about it for innovation. […]
And those relational databases from Microsoft, Oracle, and IBM? They’re essentially just updated versions of the companies’ 2004 offerings.
You’ll see these numbers in many surveys. But there are a couple of things to keep in mind while reading them:
- the enterprise world is well-known to be a late adopter. A very late adopter actually.
- many of these databases are subscription based so customers are locked-in on at least an yearly basis
- many of these databases have been acquired together with hardware and consultancy/support. Another type of lock-in.
- none of these databases is showing the growth in demand, jobs, and revenue that the top NoSQL databases are seeing for the last 12-18 months.
When you already bought a house, it’s quite difficult to go out looking for a new one. But there’s no good reason for you not to look and get the best appliances and furniture for your house.
Original title and link: 2014 State Of Database Tech: Think Retro ( ©myNoSQL)
A 3-part, a bit too high level for me, article about what is to be gained (and lost) when using Riak instead of a relational database:
What I always like about Basho’s posts is that they don’t shy away from covering the tradeoffs.
Original title and link: Relational to Riak ( ©myNoSQL)
The recent announcement of the Microsoft SQL Server 2012 release emphasized the high availability features added to this version. Here is what I could find after some digging through the documentation:
AlwaysOn Failover Cluster Instances: As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level—a failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
This is explained in more detail on AlwaysOn Failover Cluster Instances (SQL Server).
AlwaysOn Availability Groups: The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL Server 2012, AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. An availability group supports a set of read-write primary databases and one to four sets of corresponding secondary databases. Optionally, secondary databases can be made available for read-only access and/or some backup operations.
More documentation about AlwaysOn Availability groups can be found here.
Database mirroring: This feature will be removed in a future version of Microsoft SQL Server.
Log shipping: SQL Server Log shipping allows you to automatically send transaction log backups from a primary database on a primary server instance to one or more secondary databases on separate secondary server instances.
This is the well-known master-slave setup. More details can be found here.
Also worth checking the availability of these feature per SQL Server 2012 editions:
Original title and link: Microsoft SQL Server 2012 High Availability Solutions ( ©myNoSQL)