External Article

How to Get SQL Server Security Horribly Wrong

It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.

Blogs

T-SQL Tuesday #198–Change Detection

By

This month we have a new host, Meagan Longoria, who graciously agreed to help...

Redgate and Rome

By

I’m at the UK Redgate office today, meeting with senior leaders in all areas...

Quick Tip: Check Most DTU Expensive Queries in Azure SQL Database

By

Optimizing Azure SQL Database performance often begins with identifying the most resource-intensive queries. Understanding...

Read the latest Blogs

Forums

Permissions Removal When Changing Object Schema

By Brandie Tarvin

When the schema of an object is changed, SQL Server wipes out the previous...

SSRS Is Dead. Here Are Your Real Options

By sgharlow

Comments posted to this topic are about the item SSRS Is Dead. Here Are...

The Distance Metric

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Distance Metric

Visit the forum

Question of the Day

The Distance Metric

In the new VECTOR_DISTANCE() function in SQL Server 2025, the first parameter is the distance_metric. What is this?

See possible answers