Ken Powers


SQLServerCentral Article

The GO Command and the Semicolon Terminator

There are probably not many SQL Server DBAs that use the semicolon as a statement separator. In SQL Server 2005, this is required in certain places and new author Kenneth Powers brings us a look at where and why you need to use this syntax.

(22)

You rated this post out of 5. Change rating

2007-10-02 (first published: )

45,787 reads

Blogs

Don’t Miss Out – SQL Server Query Tuning Fundamentals Starts Next Monday!

By

Next Monday, February 9, 2026, my one-day live online training SQL Server Query Tuning...

Monday Monitor Tips: SQL Auditing Preview

By

One of the features we advocates have been advocating for is a better way...

SQL Server 2025 CU1 Fixes the Docker Desktop AVX Issue on macOS

By

Microsoft fixed the AVX instruction issue in SQL Server 2025 CU1. The container now...

Read the latest Blogs

Forums

25 Years of SQL Server Central

By Steve Jones - SSC Editor

Comments posted to this topic are about the item 25 Years of SQL Server...

The Decoded Value

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Decoded Value

Deploying SQL Server Developer Edition in Kubernetes: A Cost-Effective Alternative to RDS

By Sujai Krishna

Comments posted to this topic are about the item Deploying SQL Server Developer Edition...

Visit the forum

Question of the Day

The Decoded Value

In SQL Server 2025, what is returned from this code:

DECLARE @message VARCHAR(50) = 'Hello SQL Server 2025!';
DECLARE @encoded VARCHAR(MAX);

SET @encoded = BASE64_ENCODE(CAST(@message AS VARBINARY(1000)));
SELECT BASE64_DECODE(@encoded) 

See possible answers