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

Houston AI-Lytics 2026–Powerpoint Slides

By

Thanks to everyone for attending my session on running a Local LLM. If you...

The Book of Redgate: Do the Right Things

By

I do believe that Redgate has been very customer focused since it’s inception. I’ve...

GenAI vs Dashboards: Not the Same (And Never Will Be)

By

There’s a question I’ve been hearing more and more lately, especially as Copilot, Fabric,...

Read the latest Blogs

Forums

T-SQL in SQL Server 2025: JSON_ARRAYAGG

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Spring Connections and Learning at PASS On Tour

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spring Connections and Learning at...

Multiple Sequence Values

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Sequence Values

Visit the forum

Question of the Day

Multiple Sequence Values

How do I easily get the next 12 sequence values from a sequence object?

See possible answers