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

Github Copilot in SSMS can include data in its memory, simple prompt injections ahead

By

SQL Server Management Studio (SSMS) has recently added support for Github Copilot. This is...

Advice I Like: Failure

By

If it fails where you thought it would fail that is not a failure....

Logged in as a member of an Azure AD Group Error while Deploying DACPAC

By

Quite a long title for a short blog post ??While deploying a DACPAC (from...

Read the latest Blogs

Forums

Don't Create Workslop

By Steve Jones - SSC Editor

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

What is the original database name?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is the original database...

The DBScan algorithm tutorial

By Daniel Calbimonte

Comments posted to this topic are about the item The DBScan algorithm tutorial

Visit the forum

Question of the Day

What is the original database name?

What is returned when this code is run?

SELECT ORIGINAL_DB_NAME()

See possible answers