External Article

SQL Graph Objects in SQL Server 2017: the Good and the Bad

Graph databases are useful for certain types of database tasks that involve representing and traversing complex relationships between entities. These can be difficult to do in relational databases and even trickier to report on. Until now, we have had the choice of doing it awkwardly in SQL Server or having an ancillary database to tackle this type of task. SQL Server 2017 will be bringing graph capabilities to the product but will these features prove to be good enough to allow us to dispense with specialised Graph databases? Dennes Torres decided to find out.

Blogs

Reading SQL Server File Headers with DBCC FILEHEADER

By

I’ve been doing a deep dive into SQL Server on-disk structures lately, and one...

T-SQL Tuesday #197 – An impactful session or two from a conference – RECAP

By

Thanks to everyone who joined the blog party this month. I noticed three themes...

OpenClaw- Agentic Engineering

By

This week has training on AI – Cyber security experts – Omar Santos and...

Read the latest Blogs

Forums

What's new in R 4.6

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What's new in R 4.6

Interesting Changes in R

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Interesting Changes in R, which...

PostgreSQL String Functions Part 1

By Shivayan Mukherjee

Comments posted to this topic are about the item PostgreSQL String Functions Part 1

Visit the forum

Question of the Day

Identities and Sequences V

When thinking about the identity property and sequence objects, which of these can generate values before an insert statement is executed?

See possible answers