Re: row level security without views
- From: "Uri Dimant" <urid@xxxxxxxxxxx>
- Date: Wed, 27 Sep 2006 09:39:25 +0300
tables,views and roles. I wanted to know if SQL Server 2005 has any
built-in support for the row level security and I think it is not
there.
Please correct me if I am wrong.
Not , that I 'm aware
"Nikhil" <nikhilukidwe@xxxxxxxxx> wrote in message
news:1159335152.141657.291800@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Uri,
I have already seen this article. This article explains the
"implementation" of row-level security using existing constructs like
tables,views and roles. I wanted to know if SQL Server 2005 has any
built-in support for the row level security and I think it is not
there.
Please correct me if I am wrong.
Nikhil.
Uri Dimant wrote:
Hi
http://www.microsoft.com/technet/prodtechnol/sql/2005/multisec.mspx
"Nikhil" <nikhilukidwe@xxxxxxxxx> wrote in message
news:1159253428.573628.105420@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I want to implement row level security in SQL Server 2005 without
implementing views. The desired effect is firing a query on a table
like "select * from <tablename>" should return only rows which are
accessible to the logged in user. Which rows are accessible will be
decided using some data in another table. This table will have user
login name and one or more IDs associated with it. These IDs will be FK
in the table on which we fire select (or update/delete) query. I need
to device a solution such that the select query will return all rows
from the table which contain the ID that is assigned to the logged in
user. Is it possible in SQL Server 2005 without implmenting views on
each table?
Thanks in advance.
Nikhil.
.
- References:
- row level security without views
- From: Nikhil
- Re: row level security without views
- From: Uri Dimant
- Re: row level security without views
- From: Nikhil
- row level security without views
- Prev by Date: Re: Rights needed to restore DB
- Next by Date: Re: Revoke View any database from public in MSSQL 2005
- Previous by thread: Re: row level security without views
- Next by thread: sp_helprotect behaves differently compare to the SQL Server 2005 BOL
- Index(es):