Archives of the TeradataForum

Message Posted: Tue, 16 Dec 2008 @ 17:44:15 GMT

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

Sridhar -

You've been asking a lot of questions about porting Oracle to Teradata, so let me make a general suggestion: don't. (Port your code, that is; I don't have a problem w/ the questions.)

Yours is really a three-step job:

1) Really learn how Teradata works. This means understanding why you don't want to use cursors and why TD doesn't support sequences. Most importantly, it means understanding why it's (almost always) just fine to do everything you were doing sequentially in SQL.

2) Know what your Oracle code achieves in the end, not what it does step by step. Forget the contents of the code, just make sure you know what you're trying to get in the end.

3) Write Teradata-specific code to get to where you need to be. Don't look at each Oracle function or step in a proc and try to convert it. Just start with the starting data and write Teradata until you get to the end.

We went through a large conversion a couple of years ago, and the hardest and most beneficial part was forcing ourselves to stop thinking about how to make Oracle X-Y-Z become Teradata X-Y-Z and to start thinking about how to make Teradata get us to X without regard to how we used to do it.

Dave C

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