Teradata introduced QueryGrid, which allows queries to fetch data and analytics across multiple databases and Hadoop. QueryGrid coordinates different systems so a query can retrieve partial results from Teradata and other systems like Hadoop, Oracle, and SQL Server. The results are then joined in Teradata and sent to the user. QueryGrid processes data where it resides, minimizes data duplication, and enables bidirectional data movement between systems transparently.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0 ratings0% found this document useful (0 votes)
37 views1 page
Teradata: Eradata Uery RID
Teradata introduced QueryGrid, which allows queries to fetch data and analytics across multiple databases and Hadoop. QueryGrid coordinates different systems so a query can retrieve partial results from Teradata and other systems like Hadoop, Oracle, and SQL Server. The results are then joined in Teradata and sent to the user. QueryGrid processes data where it resides, minimizes data duplication, and enables bidirectional data movement between systems transparently.
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1
Teradata
TERADATA QUERY GRID:
For me the biggest news was clearly the QueryGrid. It can coordinate multiple modes of analysis across multiple databases plus Hadoop. You can run queries which can fetch data/analytics partly from teradata and partly from other heterogeneous system like hadoop, oracle, sql server etc. So basically you query teradata which inturn sent its portion of query to hive (in case you are using hadoop) then dataset return from hadoop will be joined in teradata, final result will be sent to the user Some striking features are - It processes data where it resides - Minimize data duplication - Bi directional data movement - Transparent data movement