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

The Notification Trap: How Input Fatigue Is Killing Deep Work in Tech

By

If you've been here before, you know this blog is usually about SQL Server,...

Designing a Storage Load Test for SQL Server

By

I’ve been doing storage load tests for SQL Server for a long time, both...

Questions and Answers from Running a Local LLM

By

I had a few random questions from my Running a Local LLM on Your...

Read the latest Blogs

Forums

A question about how to store the address in the database

By eichnerm

I have an app that has an address field on the customer and the...

SSIS package failing intermittently on last Excel Component

By Reh23

Good Afternoon, I have a Job which "fires" off an SSIS package (that is...

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:...

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