Archives of the TeradataForum

Message Posted: Tue, 06 Oct 2009 @ 22:00:35 GMT

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

Thanks Carrie for the insightful response.

It is very similar some functionality that I would like to achieve via TASM.

I would like to restrict/disallow DML access to views (views on top of tables used to control DML /Locking ) to a group of users based on Workload categorization type of criteria.

Here is a situation similar to what I would like to achieve:

1.) A user IS NOT allowed to run an Insert into a view from SQL Assistant and/or BTEQ.

AND

2.) The same user IS allowed to run an Insert into a view from a specific external application where their access to certain data can be restricted.

I can see how to properly categorize these things into workloads via TASM settings like ClientID, or Queryband or Application etc... , but I want an immediate rejection/abort and logging of the SQL of based on that criteria. It seems that setting the query limit to 0 is the closest I can come to that functionality and then aborting from the DELAY QUEUE, since the query actually has to run for an exception criteria for a Workload to be met.

I think what I want is something that works like the Object Access filter that is executed based on a Workload Classification, rather than a period.

Any ideas on how to achieve this, or has anyone else out there done this successfully?

Regards,

Eric W. Barner

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