Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

nosql vs relational database Expand / Collapse
Posted Tuesday, February 8, 2011 5:18 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Saturday, September 10, 2011 6:32 PM
Points: 57, Visits: 249
Hello Gurus

I am a SQL-Server developer + Development DBA (Production DBA is managed by our hosting partner)

While i was surfing the web, I came across NoSQL article (Link below). Is this something relational database guys has to be concerned about? I am concerned on what future holds for SQL-Developers and SQL-server DBAs

Any thoughts gurus?

Post #1060740
Posted Wednesday, February 9, 2011 6:37 AM



Group: General Forum Members
Last Login: Today @ 4:52 AM
Points: 17,172, Visits: 32,134
It really depends on the business. There are places where nosql is going to, rightly, kick out OLTP systems. There are places where nosql does not belong. Just as an example, I really, really don't want my banking to be done with eventual consistency.

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of:
SQL Server Query Performance Tuning
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1061067
Posted Thursday, February 10, 2011 12:48 PM

SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Tuesday, August 18, 2015 12:28 PM
Points: 30, Visits: 178
I'd suggest that you stop worrying about losing your job to something new and instead pioneer that something new. Relational databases aren't going anywhere, but they are no longer the only game in town. Non-relational databases have a lot of strengths and weaknesses that allow the to complement the strengths and weaknesses of the RDBMS.

While you don't want your banking to be done with eventual consistency, it's most likely not being done with ACID transactions. Huge banks are typically going to dump your daily transactions in some kind of queue for processing at some later time. It's just not possible to easily and cheaply get the kind of throughput that we demand when you're dealing with transactions from millions of individual customers plus mortgages and commercial customers.

Besides, with a properly designed eventually consistent system it's probably going to be faster and more error proof than a single server set up. Eventually consistent systems are, typically, "eventually" consistent over the period of several milliseconds, not minutes as many DBAs like to think. Werner Vogels wrote an excellent article about what eventual consistency and database durability mean:

Jeremiah Peschka
Microsoft SQL Server MVP
Managing Director - Brent Ozar PLF, LLC
Post #1062254
Posted Thursday, February 10, 2011 1:25 PM



Group: General Forum Members
Last Login: Wednesday, September 23, 2015 3:34 PM
Points: 5,467, Visits: 7,660
A very handy article, Jeremiah, especially the revised one. Thanks for pointing it out. Much reading to be done!

- Craig Farrell

Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

For better assistance in answering your questions | Forum Netiquette
For index/tuning help, follow these directions. |Tally Tables

Twitter: @AnyWayDBA
Post #1062282
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse