External Article

When SQL Server Performance Goes Bad: Implicit Conversions

When you're developing a database, the pressure is on to get something that works, using an efficient algorithm. When you are getting close to a release candidate, however, there are some programming habits that must be removed from the code, because they can cause unexpected performance problems. In this article, you'll learn how to detect and remove one such problem: reliance on implicit datatype conversions in your queries. We'll use a combination of plan cache queries, extended events, and SQL Monitor.

Blogs

Using CAT for Testing of Data Agents

By

In last months one of the scenarios where you can use AI has been...

Are you getting value from your reporting?

By

Do you spend so long manipulating your data into something vaguely useful that you...

The Book of Redgate: SQL Server Central

By

It was neat to stumble on this in the book, a piece by me,...

Read the latest Blogs

Forums

Microsoft Security Changes and SQL Server

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Microsoft Security Changes and SQL...

Expanding into Print

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Expanding into Print

Downtime Caused by the Postgres Transaction ID Wraparound Problem

By Chandan Shukla

Comments posted to this topic are about the item Downtime Caused by the Postgres...

Visit the forum

Question of the Day

The String Distance I

In SQL Server 2025, what is returned by this code:

SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled.

See possible answers