Introduction to Database Design - Teradata Vantage - Analytics Database

Using the Database Design Content

This document describes database design for Teradata Vantage™, including logical design and physical design, capacity considerations, and designing for tactical queries.

Why Would I Use this Content?

Use this content to properly design and configure your database so that it can provide optimal access to the stored data to answer your ad hoc, tactical, decision support, data mining, and analytic requests.

How Do I Use this Content?

Learn about the Vantage architecture so that you can take advantage of its capabilities when designing your database. See Database Design for Vantage. Follow the standard database design practices, as well as the Teradata architecture-specific physical design principles described in this document to implement your database. You can use the Sample Worksheet Forms to plan your database design projects.

How Do I Get Started?

1. Conduct a thorough analysis of your requirements to understand how the end users will use the database. See Requirements Analysis.
2. Determine the typical use cases for your data. The design of your database should optimize how it can efficiently handle these workloads. See Design Considerations and Designing for OLTP and Designing for Data Warehousing Support.
3. Apply standard database design practices to design your database:
   1. See ANSI/X3/SPARC Three Schema Architecture for a high-level and a more detailed view of the ANSI/SPARC architecture.
   2. Conduct logical data modeling to define the real world objects and their attributes that the database must represent as well as the relationships among them. The logical database design phase should include the normalization process to make sure that your resulting database is fully normalized. See Semantic Data Modeling and The Normalization Process. See also Denormalizing the Physical Schema during physical implementation of the database if performance enhancement is needed.
   3. Conduct activity transaction modeling to attach physical attributes to the entities, attributes, and relationships defined in the logical data model. See The Activity Transaction Modeling Process.
   4. Implement physical database design to create the actual databases, base tables, constraints, indexes, partitioning, views, macros, triggers, and other objects that define the physical database. See Summary Physical Design Scenario. Optimize the performance of your database by applying Teradata architecture-specific physical design principles. See Indexes and Maps, Design Issues for Tactical Queries, and Designing Tables for Optimal Performance.

References to Other Relevant Content

• Partitioned Primary Index Usage Orange Book, 541-0003869
• No Primary Index (NoPI) Table User Guide Orange Book, 541-0007565
• Increased Partition Limit and Other Partitioning Enhancements Orange Book, 541-0009027
• Teradata® Columnar Primer Orange Book, TDN0009884