Articles

SQLServerCentral Article

Deadlock Notifications in SQL Server 2005

Deadlocks do not occur too often, but when they do, it can be a time consuming and frustrating endeavor to track them down. In SQL Server 2000, you could alter the message to ensure these were written to the error log and track them down quickly. In SQL Server 2005, it is a little more tricky, but new author Patrick Leblanc brings us a technique for sending out a notification.

(24)

You rated this post out of 5. Change rating

2007-10-10

15,329 reads

SQLServerCentral Article

Migrating SQL Server 2000 DTS Packages Across Environments

Many of us still have SQL Server 2000 DTS packages running throughout our environment. New author Owais Bashir Ahmed brings us an interesting technique for moving those packages between servers that might come in handy as you continue to work on these packages in SQL Server 2000.

(8)

You rated this post out of 5. Change rating

2007-10-09

6,272 reads

Blogs

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022

By

Reality (And Limits) of Instant File Initialization for Transaction Logs in SQL Server 2022 ...

Looking Back at the Redgate 2026 Company Kickoff

By

Last week I spent a few days in Cambridge, UK for the Redgate Company...

Using AI for Git Hooks

By

Recently I had someone internally ask about whether SQL Source Control supports Git Hooks....

Read the latest Blogs

Forums

SQL Agent job running gMSA cannot backup to NAS target

By DataMatt43

I'm running a group MSA for the database engine and SQL Agent in a...

sys.query_store_query question

By as_1234

All, My query is as follows: SET DATEFORMAT dmy SELECT p.query_id, DATEADD(MICROSECOND,-rs.max_duration,rs.first_execution_time) AS starttime,...

Encoding Strings

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding Strings

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