SQLServerCentral Article

Conditional Statements in WHERE Clauses

T-SQL is a powerful language, enabling you to handle many different types of set based operations. But having flexible WHERE clauses isn't something that many DBAs deal with on a daily basis. New Author Sotiris Filippidis brings us an article on how you can structure a WHERE clause to handle all types of strange business logic without using dynamic SQL. Read on to learn more about his technique.

SQLServerCentral Article

Moving the SQL 2005 System Databases

Most SQL Server instances are installed with the default values, but that's not always the way it should be. Often there is the need to "move" databases to comply with standards, free up disk space, or some other reason. Moving the system databases can be a little tricky, but author Vince Iacoboni brings us his code and technique for easily doing this for SQL Server 2005 databases.

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

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