 |
 |
Archives of the TeradataForum
Message Posted: Wed, 18 Jun 2003 @ 20:56:06 GMT
| Subj: | | Re: Consecutive sequence sql logic |
| |
| From: | | Dave Harper |
Wow. I guess I am still new to TeraData, but I would have never thought that writing an inner join is WORSE than writing it in the where
clause. I thought all that changed pre SQL-92. Should I be writing left joins in += syntax too? Or perhaps that I am biased coming from a
Microsoft SQL Server background that HAD intuitive functions to handle many of the day to day query problems that TeraData so eloquently
doesn't handle. It is quite sad when you can't do a isnull(), isnumeric(), or other case type scenarios without writing tons of code.
I would love to hear arguments for TeraData vs. SQL Server or Oracle. The data retrieval times are a bit faster, but not nearly enough
to deal with all the issues that come up with TeraData. And on another note, why is it so buggy? I have been working with the product for
only four months, and have had three issues that I found be escalated to NCR for fixes -- I didn't think I was working with a BETA version
of the product.
Please, someone, anyone, give me some confidence in this product.
Regards.
Dave Harper
| |
