Teradata is a complex, highly-versatile RDBMS technology, matured through years of growth to provide the task-specific functionality required by its long-term clients whilst also continuing to serve as a general-purpose MPP technology for the wider market. On top of these more specifically-focussed features, each Teradata update retains functions provided by earlier releases, even if those functions have since been out-dated or upgraded, in order to support client’s legacy code.
With such a wide assortment of features, Teradata can be overwhelming, and it can be difficult to decide how to best make it work for you. Do your tables require Fallback? What are the best candidates for Primary Indexes? How regularly should you collect Statistics, and what is the best method to do so?
Making the wrong decision on a Teradata system can have obvious and drastic effects on the system's overall performance; and a poorly performing Data Warehouse can seriously impact on the business as a whole. But why spend money needlessly upgrading a Teradata system that is already sufficient, when a few simple changes could make all the difference?
Learn from the best
VLDB Solutions are expert Teradata consultants. With decades of experience developing applications for Big Data management, we have gathered a list of Teradata Best Practices to help our clients avoid common mistakes and instead fully harness the power of a Teradata system. Our Best Practice guidance can help you to write robust, balanced code that will execute smoothly, quickly, and efficiently, and stop you slowing down your system unnecessarily.