Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


nosql vs relational database


nosql vs relational database

Author
Message
sqlcool
sqlcool
Valued Member
Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)Valued Member (57 reputation)

Group: General Forum Members
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?

http://techblog.netflix.com/2011/01/nosql-at-netflix.html

http://en.wikipedia.org/wiki/NoSQL

Cheers
Grant Fritchey
Grant Fritchey
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17609 Visits: 32267
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 and SQL Server Execution Plans
Product Evangelist for Red Gate Software
Jeremiah Peschka
Jeremiah Peschka
SSC Rookie
SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)SSC Rookie (30 reputation)

Group: General Forum Members
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: http://www.allthingsdistributed.com/2007/12/eventually_consistent.html

Jeremiah Peschka
Microsoft SQL Server MVP
Managing Director - Brent Ozar PLF, LLC
Evil Kraig F
Evil Kraig F
SSCertifiable
SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)SSCertifiable (5.7K reputation)

Group: General Forum Members
Points: 5703 Visits: 7660
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search