External Article

Developing Modifications that Survive Concurrency

You can create a database under the assumption that SQL looks after all the problems of concurrency. It will probably work fine under test conditions: then, in the production environment, it starts losing data in subtle ways that defy repetition. It is every Database Developer's nightmare. In an excerpt from his acclaimed book, Alex Kuznetsov explains why it happens, and how you can avoid such problems.

Blogs

T-SQL Tuesday #198 Roundup: How Do You Detect Data Changes?

By

Thank you to everyone who participated in T-SQL Tuesday #198! When I wrote the...

Optimizing Redshift Performance by Configuring WLM Queues

By

Efficient query performance in Amazon Redshift often comes down to how well you manage...

PowerShell Strikes Back: Return of the Loop

By

Welcome back to PowerShell Strikes Back. We’re three weeks in, and the training is...

Read the latest Blogs

Forums

Dealing with huge heap tables

By JasonO

Recently, our dev teams approach me for advice on improving their huge heap table...

Merge Replication failing with Error converting data type nvarchar to numeric

By Leo.Miller

After upgrading 2 Merge Replicated databases to SQL 2022 and re-establishing the Merge Replication...

Why Your Index Isn't Being Used? - Reading Execution Plans to Find the Real Culprit

By Sanket Parmar

Comments posted to this topic are about the item Why Your Index Isn't Being...

Visit the forum

Question of the Day

Distance Metric Algorithms

What are the distance metric algorithms that can be used in VECTOR_DISTANCE()?

See possible answers