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 76: Availability Group Improvements
Episode 75 Storage Testing
Episode 74: 2016 Year in Review
Episode 73: Performance Tuning
Episode 72: Test Automation in BI
Episode 71: BI Tools of the Trade
Episode 70 SQL Server on Linux
Episode 69: Our SQL Server Setup Checklist
Episode 68: SSIS Administration
Episode 67 Dear Developer
Episode 66: Microsoft's Professional Program
Episode 65: Do you have good data architecture?
Episode 64: Certifications and Career Development
Episode 63: New Data AvailabilityFeatures in SQL Server 2016
Episode 62: Ask Me Anything--Cortana Intelligence Suite
Episode 61: The Debrief
Episode 60: What is U-SQL?
Episode 59: Mirroring, Availability Groups, Replication, and Log shipping
Episode 58: 4 ways to stay sharp with technical learning
Episode 57: What SQL Server feature would you change?
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