Additional Articles


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.

2020-09-11

Blogs

2025 Wrapped for Steve

By

I’ve often done some analysis of my year in different ways. Last year I...

The Book of Redgate: Spread across the world

By

This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...

Merry Christmas

By

Today is Christmas and while I do not expect anybody to actual be reading...

Read the latest Blogs

Forums

Database security permissions save script

By Srinivas Merugu

Comments posted to this topic are about the item Database security permissions save script

Database backup job steps

By Pete Bishop

I have a SQL Agent job for backing up a set of Analysis Services...

SQL Server 2025 Backup Compression Algorithm

By Johan Bijnens

Comments posted to this topic are about the item SQL Server 2025 Backup Compression...

Visit the forum

Question of the Day

The Large Encoded Value

I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?

See possible answers