Articles

SQLServerCentral Article

Maximum Capacity Specifications in SQL Server 2005

SQL Server 2005, the next evolution of SQL Server, should be growing the capacities as well as the capabilities of the product. With some research, Steve Jones brings you the best current information he could find about SQL Server 2005, comared with the SQL Server 7 and 2000 values.

(3)

You rated this post out of 5. Change rating

2007-01-26 (first published: )

41,907 reads

SQLServerCentral Article

Building a Distributed Service Broker Application

Service Broker is one of the more interesting and useful new enhancements in SQL Server 2005, however many DBAs are not familiar with this subsystem. New author Santhi Indukuri brings us a practical example of how you can build a distributed application using Service Broker.

(18)

You rated this post out of 5. Change rating

2007-01-25

18,946 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