External Article

Selecting the database recovery model to ensure proper backups

One of the first things that should be done when managing SQL Server is to setup an appropriate backup plan in order to minimize any data loss in the event of a failure. Along with setting up a backup plan there are certain database configurations that need to be setup to ensure you are able to backup databases correctly. In this tip we will look at the different recovery models that SQL Server offers and how to choose a recovery model for your database.

Technical Article

Trash Destination Adapter

The Trash Destination and this article came from early experiences of using SSIS and community feedback at the time. When developing a package it is very useful to have a destination adapter that does nothing but consume rows with no setup requirement. You often want run a package part way through development, or just add a path so you can set a Data Viewer.

Blogs

Looking Back at the Redgate 2026 Company Kickoff

By

Last week I spent a few days in Cambridge, UK for the Redgate Company...

Using AI for Git Hooks

By

Recently I had someone internally ask about whether SQL Source Control supports Git Hooks....

Flyway Tips: AI Helps with Commit Messages

By

At Redgate, we’re experimenting with how AI can help developers and DBAs become better...

Read the latest Blogs

Forums

SQL Agent job running gMSA cannot backup to NAS target

By DataMatt43

I'm running a group MSA for the database engine and SQL Agent in a...

sys.query_store_query question

By as_1234

All, My query is as follows: SET DATEFORMAT dmy SELECT p.query_id, DATEADD(MICROSECOND,-rs.max_duration,rs.first_execution_time) AS starttime,...

Encoding Strings

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding Strings

Visit the forum

Question of the Day

Encoding Strings

I have this code in SQL Server 2025. What is the result? 

DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!';
DECLARE @encoded VARCHAR(MAX);

SET @encoded = BASE64_ENCODE(@message);
SELECT @encoded AS EncodedResult;

See possible answers