Archives of the TeradataForum

Message Posted: Sun, 01 Feb 2004 @ 13:02:59 GMT

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

A-Team

Has anyone successfully come up with a way to provide row and/or column level security in Teradata?

We have been mandated to provide row level security and also column level security from one of our customers.

I do not believe that the source system has this in place today, but in order to place the data in the warehouse, they are demanding this level of security. (well... OK!)

For this particular application, there are only a few limitations that are required such as: "If you belong to a certain department you can see these columns and these rows." (So far so good...)

So we built a few security tables and then built what we like to call "Shield Views" that restrict the rows using WHERE Criteria... Simple enough so far...

The challenge of course is the columns. We have placed CASE statements in the views to determine whether to return data or not based on the security criteria. (This is starting to get painful.)

First question for those who have dared the improbable.

How much of a performance hit are we looking at approaching security at a row and column level?

What functions or characteristics are built into Teradata to accommodate this level of security?

Is there a better way that will be more manageable?

Your thoughts and direction are welcome...

Chris Coffing
Chief Information Officer
Coffing Data Warehousing
www.coffingdw.com

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