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

Advice I Like: Rewards from Work

By

The greatest rewards come from working on something that nobody has words for. If...

Overcoming Challenges: Navigating Common Pitfalls in FinOps Adoption

By

Working in DevOps, I’ve seen FinOps do amazing things for cloud cost control, but...

Why your data still can’t answer a simple question 

By

Every organization I talk to has the same problem dressed up in different clothes....

Read the latest Blogs

Forums

The day-to-day pressures of a DBA team, and how we can work smarter with automation and AI

By Terry Jago

Comments posted to this topic are about the item The day-to-day pressures of a...

Analysis Services Model w/ Direct Query and (Default Veritpaq)

By Archivist

Analysis Services (either the integrated workspace in Power BI or on a SQL Server)...

Don't Panic

By Grant Fritchey

Comments posted to this topic are about the item Don't Panic

Visit the forum

Question of the Day

Identities and Sequences IV

When thinking about the identity property and sequence objects, which of these can be used with numeric and decimal data types?

See possible answers