Articles

External Article

Using the kill to cure

Code profiling tools can help cure most performance problems, but sometimes the problem is so severe that you'll first need to know how to wield computing's least understood tool, the debugger, before diving in with the Profiler. Brian Donahue, Crash Scene Investigator, is on hand to explain why.

2007-11-02

2,944 reads

SQLServerCentral Article

Getting the Most Out of SQL Server 2000's Query Analyzer, Part III

In this article, Brian Kelley continues his series on Query Analyzer for SQL Server 2000. Query Analyzer offers a highly configurable integrated development environment (IDE). Some of the areas Brian looks at are how to modify the fonts and colors, set connection settings, choose scripting options, and customizing file and result set options. Learn how to make the most of the IDE and make it work for you.

(1)

You rated this post out of 5. Change rating

2007-11-01 (first published: )

38,991 reads

Blogs

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...

Startup scripts in SQL Server containers

By

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

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