• SQL Problems

  • SQL “Union ALL” vs. “Union”
  • Using TIMESTAMP datatype to reduce database corruption
  • GETUTCDATE vs. GETDATE with timezones and daylight savings
  • Using SQL Server Managment Studio SQL Icon to update records
  • SQL Server Database Mirroring vs. Double-Take
  • SQL Aggregate BIT Columns with Group By

• Quick Links

  • High Availability
  • Solutions to Unusual Problems
  • SQL Server Database
  • SQL Server Management
  • SQL Server Query Analyzer
  • SQL Tips and Tricks
  • Uncategorized

Sometimes, you might need to get a record set of the UNION of two SELECT’s but you don’t want to remove duplicates.  This might happen if you were just needing a proper count of the rows or if you just wanted to check something before deleting a bunch of rows.

The simple way to do this is with UNION ALL.

A UNION statement returns the UNION of two SELECT’s but removes duplicates.  If you use UNION ALL, the records returned are all the records including duplicates.

Go Back

Rate This Article

• 
  

• SQL Server Poll

  • Is Double-Take Better Than SQL Server Database Mirroring?

    • Yes, Double-Take is Much Better
    • About The Same
    • No, I Perfer Database Mirroring

    View Results

     Loading ...
  • Polls Archive

Highest Rated Article

• SQL Aggregate BIT Columns with Group By (5.00 out of 5)
• Using TIMESTAMP datatype to reduce database corruption (5.00 out of 5)
• SQL Server Polls (0.00 out of 5)
• Contact Us (0.00 out of 5)
• Sitemap (0.00 out of 5)
• SQL Server Toolkit (0.00 out of 5)
• SQL Server Database Mirroring vs. Double-Take (0.00 out of 5)
• Using SQL Server Managment Studio SQL Icon to update records (0.00 out of 5)
• GETUTCDATE vs. GETDATE with timezones and daylight savings (0.00 out of 5)
• SQL “Union ALL” vs. “Union” (0.00 out of 5)