Share

Teradata Pro is now DWH Pro!

teradata volatile table
problem-solving

As always, when something comes to the attention of a larger number of people, some embrace it, some frown.

We were asked to dissociate the name of this website from the term Teradata.We do so to avoid any future misunderstanding, irrespective of any admission of fault.

Y

ou will find us at www.dwhpro.com from now on.Since we respect copyright and trademark law and therefore accept to alter any of the content or design that creates the impression of an infringement of rights, we also respect and hold high the values of freedom of speech and free expression and exchange of thoughts and opinions on technologies or products.


Want more practical data engineering analysis like this?

Join DWHPro Letters and get field-tested notes on Teradata, Snowflake, AI, migrations, performance, and enterprise data work. DWHPro Letters is free. Subscribe to get new issues by email.

Get the next issue



Planning or surviving an enterprise data platform migration?

I write regularly about the performance, cost, architecture, and project mistakes that show up in real Teradata, Snowflake, Databricks, and enterprise data work.

Subscribe for free and keep launch access.

Written by Roland Wenzlofsky, founder of DWHPro and author of Teradata Query Performance Tuning. DWHPro has helped data warehouse practitioners for 15+ years.

Subscribe to DWHPro Letters

Practical field notes on enterprise data engineering, production AI systems, platform migration, and the senior engineering market.
Written by Roland Wenzlofsky Founder of DWHPro Author of Teradata Query Performance Tuning
Get the next issue
Subscribe