Articles

Technical Article

Beware the REPLACE function when doing heavy string parsing

I found something interesting the other day. I was attempting to optimize a very heavy string parsing routine using T-SQL and was having problems. I don’t normally use T-SQL for such heavy string parsing, but this was a special case of a legacy structure that I had to work with, so I had no choice.

You rated this post out of 5. Change rating

2009-08-27

5,504 reads

Technical Article

A True SQL OS

SQL Server is so large and complex that it's like an operating system. In fact, there the core engine is often referred to as the "SQL OS" by Microsoft developers. Steve Jones would like to see SQL Server as it's own OS at some point.

You rated this post out of 5. Change rating

2009-08-26

787 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

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

The Large Encoded Value

By Steve Jones - SSC Editor

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

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