The majority of the topics covered by this document apply to designing for strategic, or decision support, queries. Because you can also run your operational data store on Database Engine 20, this section highlights design issues you must consider when implementing a physical design to support mixed workloads of both strategic and tactical queries.
The document discusses other material related to more specific design issues for tactical queries in Primary Index, Primary AMP Index, and NoPI Objects and Join Indexes.
The section does not make suggestions about scheduling job priorities to achieve an optimal mix of strategic and tactical workloads for your system or describe the locking issues associated with tactical queries.
See Locking Issues with Tactical Queries for information about lock management for tactical queries.
- Tactical Queries Defined
- Scalability Considerations for Tactical Queries
- Localizing the Work
- Database Design Techniques to Support Localized Work
- Single-AMP Queries and Partitioned Tables
- Recommendations for Tactical Queries and Row-Partitioned Tables
- Sparse Join Indexes and Tactical Queries
- All-AMP Queries
- All-AMP Tactical Queries and Partitioned Tables
- Application Opportunities for Tactical Queries
- Other Tools Useful for Monitoring and Managing Tactical Queries
- Monitoring Active Work