Articles

SQLServerCentral Article

Check Your Backup Compliance Against a Data Management Provider

As a database administrator, it's your responsibility to ensure the customer data won't get lost in case of a disaster, so you either provide your own backup strategy, use a third-party script, or hire a data management provider. With the first two options, you have full control over your environment so you can know exactly […]

(1)

You rated this post out of 5. Change rating

2020-04-02

1,298 reads

SQLServerCentral Article

SQL v.Next Gets Native Python in SQL Server

The next version of SQL Server is in early preview and there is a new feature that is going to be very useful for large enterprises that want to run Big Data Clusters and perform additional data science tasks. Instead of embedding Python code in a string and submitting it to the Launchpad engine, we […]

(3)

You rated this post out of 5. Change rating

2020-04-01

4,399 reads

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