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 156: Social Intelligence
Episode 155: Data Science
Episode 154: Test Driven Development
Episode 153: SQL Trail 2018 Retrospective
Episode 152: Do you use Analysis Services?
Episode 151: Azure SQL Database Managed Instance
Episode 150: The SQL Data Partners Team
Episode 149: Managing lots of databases
Episode 148: High Performance SSRS
Episode 147: Always Encrypted
Episode 146: SQL Trail Speakers
Episode 145: Is SSIS still relevant? Part 2
Episode 144: Is SSIS still relevant? Part 1
Episode 143: Transitioning from DBA to Data Warehouse Architect
Episode 142: Do You Have a HEAP of Hurting?
Episode 141: Wait, Wait, What?
Episode 140: Why data types matter
Episode 139: Getting Started with SQL Server in Azure
Episode 138: Meeting of the Minds
Episode 137: You want to work with Analytics?
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
Acquired