Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Mon, 05 Dec 2005 @ 10:12:11 GMT

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

Subj:   Re: EXPLAIN rights
From:   Dunweber, Ole

Anomy wrote:

  "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?"  

I agree that an explain should be run in the production box. But not with the developers user-id!

Because he/she will not be running the query on the production box. Or if so, he/she must have the access anyway.

I don't know if this particular case is for ETL, but when we code ETL-scripts we do the following through our configuration management tool:

Every SQL-statement in the script is EXPLAINed on the production box, using the logon-user that will be used when the script eventually executes in production (a project-user we call this).

This way we can check for syntax errors, AND also that the project-user has the necessary access rights.

So I'm quite pleased with the fact, that Teradata checks access rights when EXPLAINing a query!

Regarding your two choices, number 1 don't make sence, but number 2 does - the user id used should be one with the access rights needed by the production user(s) runnning the query.

Best Regards,

Ole Dunweber
Coop Nordic

  <Prev Next>   <<First <Prev Next> Last>>  
  Top Home Privacy Feedback  
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 28 Jun 2020