SQLEspresso

Blog Post

Adaptive Joins in SQL Server

SQL Server 2017 (compatibility 140) brought us many Intelligent Query Processing (IQP), formally known as Adaptive Query Processing, features that improve performance on workloads straight out of the box...

2020-09-10 (first published: )

1,609 reads

Blog Post

Adaptive Joins in SQL Server

SQL Server 2017 (compatibility 140) brought us many Intelligent Query Processing (IQP), formally known as Adaptive Query Processing, features that improve performance on workloads straight out of the box...

2020-09-02

25 reads

Blog Post

Open Letter to PASS

As you know, I spoke to 12 Chapter Leaders and 4 Regional Mentors yesterday. All are very upset with PASS right now and feel slighted, which as a volunteer...

2020-07-03 (first published: )

261 reads

Blog Post

Open Letter to PASS

As you know, I spoke to 12 Chapter Leaders and 4 Regional Mentors yesterday. All are very upset with PASS right now and feel slighted, which as a volunteer...

2020-06-19

4 reads

Blogs

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...

Self-Hosting a Photo Server the Whole Family Can Use

By

Until recently, my family's 90,000+ photos have been hidden away in the depths of...

Read the latest Blogs

Forums

SQL Server 2025 Backup Compression Algorithm

By Johan Bijnens

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

The Large Encoded Value

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Large Encoded Value

The Side Job

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Side Job

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