Examples of using Query performance in English and their translations into Spanish
{-}
-
Colloquial
-
Official
Display and interpret basic query performance data.
Select the Query performance tab in the main screen.
For more information,see Improving Query Performance.
Decent query performance simultaneous with high insert rates.
The data is denormalized to improve query performance.
Better understand query performance with the new explain() method.
Using ETL Jobs to Optimize Query Performance.
There are query performance issues due to sequential access to the NDB storage engine;
Identify best practices for optimizing query performance.
This improves query performance by reducing I/O requirements.
Use customization attributes to improve query performance.
Better JDBC query performance with page-size improvements, returning 1,000 rows instead of 100.
Filtering your partitions improves query performance and reduces costs.
Additionally, a combination of XML indices and relational indexes can further improve query performance.
Data formats have a large impact on query performance and query costs in Athena.
The following sections explain how to use indexes to cluster data and improve query performance.
This feature can improve query performance when you need to join a large amount of data by using an equijoin.
For more information, see Improving Database Query Performance.
Spatial indexing improves query performance on large datasets for queries that use spatial data.
Manage database objects to aid query performance.
Your Amazon Athena query performance improves if you convert your data into open source columnar formats, such as Apache Parquet or ORC.
SQL Server Profiler adds some overhead that affects query performance.
So far we have only discussed query performance, but SQL is not only about queries. .
The amount of data written by a query impacts query performance(I/O).
To improve query performance and reduce costs, we recommend that you partition your data and use open source columnar formats for storage in Amazon S3, such as Apache Parquet or ORC.
However, there are additional issues that affect query performance with linked tables.
The undesirable trade-off between additional ETL cost and slow query performance has ensured that most commercial OLAP tools now use a"Hybrid OLAP"(HOLAP) approach, which allows the model designer to decide which portion of the data will be stored in MOLAP and which portion in ROLAP.
AWS Glue jobs can help you transform data to a format that optimizes query performance in Athena.
A separate data directory is created for each specified combination,which can improve query performance in some circumstances.