The Mystery Surrounding Teradata SELECT *

Dear Reader,

Have you ever wondered why Teradata SELECT * is often considered slow and resource-intensive, despite having all columns readily available in memory?

If so, you're not alone. In our upcoming blog post, we delve into the factors contributing to this perception and investigate whether Teradata SELECT * is as poor in performance as it's made out to be.

One intriguing question we explore is why a database must access all rows and columns when retrieving and storing a data block in the cache. By understanding this process, we hope to illuminate the mysteries surrounding Teradata SELECT * and its impact on database performance.

Don't miss out on this fascinating article:

Read Now...

Best regards,

Roland - DWHPro