2016-02-25
158 reads
Editorials
2016-02-23
145 reads
2016-02-22
123 reads
2016-02-22
340 reads
Why Log Shipping is still a viable solution in 2016
An explanation as to what Log Shipping is and why it's still a viable solution in 2016.
2016-02-18
562 reads
Forcing Strong Passwords
Passwords are always a challenge, but are bad passwords the users' fault? Steve Jones has a few thoughts.
2016-02-17
105 reads
Should Production Databases Be in a VCS?
Steve Jones talks version control, but from the production perspective.
2016-02-16
104 reads
Zero Downtime for 2016
Someone made a call to architect zero downtime for databases. Steve Jones isn't sure this is the best thing you could do.
2016-02-15
158 reads
The Push to Upgrade from SQL Server 2005
There's a push to upgrade those SQL Server 2005 instances with support ending this April.
2016-02-12
118 reads
Reasonable Timeframes
Steve Jones talks about the timeframes for updating and fixing security problems in applications.
2016-02-11
88 reads
Blogs
The Book of Redgate: Spread across the world
By Steve Jones
This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...
Merry Christmas
By John
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 Bert Wagner
Until recently, my family's 90,000+ photos have been hidden away in the depths of...
Forums
Database backup job steps
I have a SQL Agent job for backing up a set of Analysis Services...
SQL Server 2025 Backup Compression Algorithm
Comments posted to this topic are about the item SQL Server 2025 Backup Compression...
The Large Encoded Value
Comments posted to this topic are about the item The Large Encoded Value
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