SQLServerCentral Editorial

Dataphor

Over the years, there have been several attempts to turn conventional RDBMSs into object relational databases, by inserting an intermediate layer. The driving force behind this was the generally-held assumption that the relational model could not handle complex data types.

SQLServerCentral Editorial

Rules, Defaults and the SQL Standard

I see, with some relief that the threatened removal of Rules and Defaults in SQL Server 2008 hasn’t happened. There has been a stay of execution. Even though they are documented, they still come with a dire warning that they are deprecated and will be removed in future versions. They have fallen foul of the SQL Standards committee, and we are now supposed to use check constraints instead.

Blogs

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

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

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