Books online state: “There is nothing a graph database can achieve, which cannot be achieved using a relational database.” Why then are we putting graph technology in SQL Server? To help me answer this question, I invite my friend AZ to chat about the Graph feature in SQL Server 2017 and introduce how graph differs from a relational model. If you have every tried to implement complicated hierarchies in SQL Server, you know what a pain this can be. I, for one, am hopeful this new feature will allow us to tackle the various relationships even though it may be lacking certain features compared with other graph databases.
Are you using graph technology in SQL Server or even another platform? I would be very interested to getting your thoughts on what you like and what you still find painful.
The show notes from today's episode can be found at http://sqldatapartners.com/2018/03/28/episode-129-graph-databases. Have fun on the SQL Trail.
Episode 136: Devops with Visual Studio
Episode 135: Seinfeld Episode
Episode 134: CosmosDB
Episode 133: Shrinking Files
Episode 132: What technologists can learn from superheroes
Episode 131: Big Data Solutions in the Cloud
Episode 130: Use Case for PowerShell
Episode 128: Database Doing DevOps
Episode 127: Developing in the database
Episode 126: SQLSaturday Edition
Episode 125: You must be an engineer
Episode 124: Beyond the runbook; DR Organization
Episode 123: Top 5 things to know when getting admin access
Episode 122: Isolation Levels
Episode 121: What makes a good manager?
Episode 120: SQL Injection
Episode 119: Getting started with GitHub
Episode 118: How has index maintenance changed?
Episode 117: PASS Summit Retrospective
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast