TSQL Tuesday – But I was Late
I was late to the game having discovered the Blog Post the day after entries were allowed. Despite that, I...
2010-01-14
834 reads
I was late to the game having discovered the Blog Post the day after entries were allowed. Despite that, I...
2010-01-14
834 reads
In Part I, I discussed a couple of scripts that could be used to help discover some vital information about...
2010-01-13
639 reads
This past week I had the opportunity to have lunch with a vendor at his clients’ site. As a part...
2010-01-10
518 reads
Like a lemming in the DBA community, I too am going to post my 2010 goals. I am looking to...
2010-01-08
465 reads
Steve Jones at SqlServerCentral.com has created a Blog for me over there at SqlServerCentral.com. I will be syndicated there and...
2010-01-07
605 reads
As a part of my DB documentation process for a large database, I needed a method to quickly show me...
2010-01-05
703 reads
I have been pondering over my local PASS chapter and participation. And more specifically about why I should participate, and...
2010-01-04
990 reads
2009-12-21
5,098 reads
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
By John
Today is Christmas and while I do not expect anybody to actual be reading...
By Bert Wagner
Until recently, my family's 90,000+ photos have been hidden away in the depths of...
Comments posted to this topic are about the item SQL Server 2025 Backup Compression...
Comments posted to this topic are about the item The Large Encoded Value
Comments posted to this topic are about the item The Side Job
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