Ars Technica

Correlated Subquery MUCH slower than same query using temp tables: Not enough RAM?

I wrote a query (with lots of help, see my painfully plentiful other threads) using a correlated subquery and it takes 5.78 seconds PER RECORD to return results. The SAME query, only I select the ...
Ars Technica

[SQL] Handle SELECT INTO #TempTable In IF/ELSE Statement

What the best way to work around this? I have the same SELECT statement but there are different criteria depending on the IF check. Well, if you happen to be using Sql Server you can do that sort of ...
TechRepublic

How to query multiple tables in SQL

Read this SQL tutorial to learn when to use SELECT, JOIN, subselects and UNION to access multiple tables with a single statement. It’s sometimes difficult to know which SQL syntax to use when ...
InfoWorld

SQL unleashed: 9 ways to speed up your SQL queries

A common SQL habit is to use SELECT * on a query, because it’s tedious to list all the columns you need. Plus, sometimes those columns may change over time, so why not just do things the easy way? But ...
Techaeris

SQL views, materialized views, and tables: What scenarios are best for each?

Although tables in SQL databases typically contain massive amounts of data, they’re not always in a format that can be used by data analysts. The data records in these tables need to be filtered ...