Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Tue, 27 Nov 2012 @ 20:24:45 GMT

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

Subj:   Re: Restriction on Space Movement
From:   Dave Wellman


Filters and throttles won't help, those are for workload management, not security - which is effectively what this is.

I also don't think that AccessRights will help you here. The problem is that the GIVE command needs CREATE DATABASE on the recipient. But you probably already know that!

I think you probably need to investigate using a stored procedure.

- accept two parameters, target_dbname and space_to_move

- code a SELECT against a lookup table which lists whether the target_dbname is acceptable for the user executing the SP

- if it is, then build and execute the command to move the space. Doing this also allows you to control which db the sapce is moved from.

- to do this I think you have to define the SP using the SQL SECURITY option as DEFINER, which is the default. (I have to be honest and say that I'm not certain of this bit as I haven't done a lot of work in this area with SP's. Maybe someone more enlightened than me can clarify this area).



Ward Analytics Ltd - Information in motion (www.ward-analytics.com)

  <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