External Article

Showplan Operator of the Week – BookMark/Key Lookup

Fabiano continues in his mission to describe the major Showplan Operators used by SQL Server's Query Optimiser. This week he meets a star, the Key Lookup, a stalwart performer, but most famous for its role in ill-performing queries where an index does not 'cover' the data required to execute the query. If you understand why, and in what circumstances, key lookups are slow, it helps greatly with optimising query performance.

Blogs

Down the Rabbit Hole: Dealing with Ad-Hoc Data Requests

By

"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...

Adding a Local Model to Ollama through the GUI

By

I saw some good reviews of the small gemma3 model in a few places...

Connect resiliently to SQL Server

By

 Why you should connect resiliently to SQL Server Transient failures happen — in the cloud...

Read the latest Blogs

Forums

Some query values change when query is run but not others. Why?

By water490

Hi everyone I have a 1000 line SQL query that is too long to...

using different credentials when debugging ssis

By stan

hi, now and then i want one connection in my ssis pkgs to use...

AlwaysON health check alerts

By Srinivas Merugu

Comments posted to this topic are about the item AlwaysON health check alerts

Visit the forum

Question of the Day

PWDCompare

What does the PWDCOMPARE function do?

See possible answers