Articles

External Article

UNION vs. UNION ALL in SQL Server

Sometimes there is a need to combine data from multiple tables or views into one comprehensive dataset. This may be for like tables within the same database or maybe there is a need to combine like data across databases or even across servers. I have read about the UNION and UNION ALL commands, but how do these work and how do they differ?

2019-12-05

SQLServerCentral Article

It's More Than What You Know

I'm a firm believer in keeping your tech skills up to date, as well as your social skills, What better way than attending or presenting at a conference or group meeting. The reason to attend an event I'm very fortunate that my company allows me training days and time for personal development, covering all expenses […]

You rated this post out of 5. Change rating

2019-12-03

1,955 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...

PASS Data Community Summit 2025 Recap

By

This is long overdue but life and distractions happened. It’s been a little over...

Read the latest Blogs

Forums

Microsoft no longer being supported?

By Richard.Westhaver

The word is finally out that Microsoft is no longer supporting SSRS. I just...

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

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