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 56: What is your favorite SQL Server 2016 Feature?
Episode 55: The new and improved SQL Server Reporting Services
Episode 54: An Executive Panel Interview
Episode 53: THE Argenis Fernandez interview on storage
Episode 52: Statistics are coming to the DB R you ready?
Episode 51: A PowerShell Story
Episode 50: SQL Server Settings
Epsidode 49: Temp Tables VS Table Variables
Episode 48: Is the Data Warehouse Dead?
Episode 47: Helping Your Data Find A Home
Episode 46: Unraveling Code
Episode 45 Service Broker
Episode 44: Azure SQL Data Warehouse
Episode 43: Why is ETL so hard?
Episode 42: Who made that change? Find out with Auditing
Episode 41: Index Maintenance
Episode 40: SQL Server Compression
Episode 39: Set statistics and StatisticsParser.com
Episode 38: SQL Server 2016 Feature Review
Episode 37: PowerBI and the DBA
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