Articles

SQLServerCentral Article

Introduction to SQL Server Everywhere

SQL Server 2005 has grown to include more versions of the platform than ever before. One of the newest is SQL Server Everywhere, now known as SQL Server Compact Edition. Jacob Sebastian brings us a great introduction for you to understand how this version disappears from the others and where it can be used.

(1)

You rated this post out of 5. Change rating

2007-06-13

8,001 reads

External Article

How to Read Raw Files in SSIS

If you've ever used SQL Server 2005 Integration Services (SSIS), you will have come across raw files. Microsoft introduced them with SSIS as a mechanism for storing data on the local file system. The design of raw files enables data to be written very quickly but, unfortunately, to achieve this performance Microsoft has used a proprietary binary storage format.

2007-06-07

3,167 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