SQLServerCentral Editorial

The Train to Katmai

We don't have a release date, the final feature set has yet to be released, but slowly I can see the train building steam. This week I found a number of blogs starting to look at various aspects of SQL Server 2008. If you look through the newsletter, you'll see coverage of data compression, clustering […]

Technical Article

Write custom trace files in TSQL

SQL Server 2005's default trace is great for monitoring system information and for finding out what happened on your server after problems occur. However, there are times when the events that the default captures are not what you need. Here are instructions for how you can create your own trace files in TSQL to catch events on your database machine.

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