|
Archives of the TeradataForumMessage Posted: Fri, 02 Dec 2005 @ 16:01:00 GMT
<-- Anonymously Posted: Friday, December 02, 2005 10:40 --> Thank you for the replies to my question. I think calling it a bug was too generous on my part as this is obviously a lack of competitive foresight on Teradata's part since other RDBMS vendors let you do it. IMHO, a developer should be able to run an explain in the production box to verify the query will run OK in the production environment, not just in the development environment. As it stands I have two choices: 1. I get to do the EXPLAINS 2. Give them a user id that has the rights Can anyone see the problems with those two choices? Sure there is the TSET concept but that's bubble gum and bailing wire to cover a serious deficiency on Teradata. NCR has to read and learn about the move towards smart RDBMS that self-manage and require less and less DBA intervention. This EXPLAIN deficiency counters that. Anonym
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||