Articles

External Article

Why Would I Ever Need to Partition My Big ‘Raw’ Data?

Whether you are running an RDBMS, or a Big Data system, it is important to consider your data-partitioning strategy. As the volume of data grows, so it becomes increasingly important to match the way you partition your data to the way it is queried, to allow 'pruning' optimisation. When you have huge imports of data to consider, it can get complicated. Bartosz explains how to get things right; not perfect but wisely.

2016-11-22

3,345 reads

External Article

How to Start Big Data with Apache Spark

It is worth getting familiar with Apache Spark because it a fast and general engine for large-scale data processing and you can use you existing SQL skills to get going with analysis of the type and volume of semi-structured data that would be awkward for a relational database. With an IDE such as Databricks you can very quickly get hands-on experience with an interesting technology.

2016-11-18

3,131 reads

Blogs

Flyway Tips: AI Helps with Commit Messages

By

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

Startup scripts in SQL Server containers

By

I was messing around performing investigative work on a pod running SQL Server 2025...

Using SQL Compare with Redgate Data Modeler

By

Redgate recently released SQL Compare v16, which included a new feature to work with...

Read the latest Blogs

Forums

Encoding Strings

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding Strings

Deep Learning and Craftsmanship Matter

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Deep Learning and Craftsmanship Matter

Building a Real-Time Analytics Pipeline with Azure Stream Analytics and SQL Server

By AR

Comments posted to this topic are about the item Building a Real-Time Analytics Pipeline...

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