Additional Articles


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.

2017-09-07

3,818 reads

Blogs

The Mystery of SQL Server 2025’s New Tricks – Scooby Dooing Episode 5

By

Every Scooby-Doo mystery starts with a haunted house, a strange villain, and a trail...

A Prompt AI Experiment

By

Prompt AI released recently and I decided to try a few things with the...

SQL Server Is Slow (part 1 of 4)

By

How should you respond when you get the dreaded Email/Slack/Text/DriveBy from someone yelling at...

Read the latest Blogs

Forums

Rounding Off issue in SQL Server

By vikramchander90

I am using Microsoft SQL Server 2022 (RTM-CU17) (KB5048038) - 16.0.4175.1 (X64)  Microsoft Corporation...

how to get notification that my database has corssed 8gb

By rajemessage 14195

i have sqlexpress on rds, is there any way i can get notifacation that...

SQL Server, Heaps and Fragmentation

By dbakevlar

Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation

Visit the forum

Question of the Day

SQL Server, Heaps and Fragmentation

A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?

See possible answers