
Speed on large datasets is the main reason we use it. We run analytical queries over tens of millions of rows daily. Before Teradata, those queries would time out or take twenty minutes. Now most finish in a few seconds.
The parallel processing handles volume differently than regular databases. Adding more nodes actually scales performance, so growth doesn't mean slowdowns. We've doubled our data volume in two years and query times stayed the same.
Being able to run Python analytics where the data lives saves us a ton of time. Our data science team used to extract data, move it to separate tools, run models, then bring results back. Now they write scripts that execute inside Teradata. No moving data around, no sampling, no waiting. Review collected by and hosted on G2.com.
The learning curve is steep. The platform has so many features that new team members spend weeks getting comfortable. It's not something you hand to a junior analyst on their first week. One new hire told me it felt like learning a new language.
Pricing is high compared to cloud alternatives. We looked at Snowflake and BigQuery recently. Both were cheaper for our usage patterns. But migrating off Teradata would be a massive project, so we're staying for now.
Documentation could be clearer. When we run into issues, finding answers sometimes means digging through support case comments instead of published docs. The community forums aren't as active as I'd like.
Query tuning for complex SQL is non-trivial. The explain plans aren't always easy to interpret, and optimization often requires deep expertise. Our best analyst spends a lot of time on this. Review collected by and hosted on G2.com.