Archives of the TeradataForum

Message Posted: Mon, 04 Nov 2002 @ 16:59:05 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

If I'm understanding the term here correctly, Teradata also does "procedural caching". In other words, Teradata will cache the optimized plan of a query for possible use by subsequent queries. There is more to it than that, but the simple answer is "yes".

However, I have to agree with Darwin that procedural caching is not the likely explanation for the difference.

Like SQL Server, Teradata also does data caching, so that if the table is small enough to fit into the available memory assigned for data caching, physical I/O will be not be required.

I would guess that Eric Kohut is on the right track with the physical design. I would guess that you're physical design for Teradata is not optimal while the SQL Server model is.

The other consideration would be the relative workloads on both systems. Are the workloads on both systems controlled so that the same relative resources are available between tests. Obviously, the best way to guarantee that would be to eliminate all other work. However, that might not be feasible.

Hope this helps.

Thomas F. Stanek
TFS Consulting
www.tfsconsulting.com

	<Prev	Next>		<<First	<Prev	Next>	Last>>