Unraveling the Web of Relationships: Understanding Graph Data
summary
Starts from the 1736 Seven Bridges problem and claims graph databases excel when relationships—not entities—drive value, especially for pattern matching, recommendations, fraud detection, geospatial routing and complex hierarchies. Covers practical SQL Server approaches (adjacency lists, path enumeration/hierarchyid, nested sets) and points out SQL Graph exists but Microsoft seems to have abandoned it. Introduces storage models (native vs multimodel), graph types (property vs RDF) and tools like Neo4j and TigerGraph, and stresses budget, talent and doing a proof of concept.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:33Why graph data matters
- 2:36Graph theory history
- 3:39What is graph data
- 5:02Graph data applications
- 6:28Is your data graph-like
- 9:16Tools and budget for graphs
- 10:18Questions before graph adoption
- 11:41Graph algorithms in SQL Server
- 13:07What is a graph database
- 14:11Types of graph databases
- 15:56Graph query languages
- 16:38Relational vs graph differences
related talks
19mUnraveling the Web of Relationships: Understanding Graph Data
19mUnraveling the Web of Relationships: Understanding Graph Data
55mA Practical Guide to Graph Databases
32mUnderstanding Complexly Connected Data using Graph Databases
29mThinking in Graphs – An Intro to Graph Databases & Applications
56mWhat are Graph Databases and Why should I care?
46mGraph Databases: Talking about your Data Relationships with Python
26mGraph Databases will change your (freakin') life
