Re: Field Level Security
From: Fernando G. Guerrero (fernan@guerrerog.org)
Date: 09/17/02
- Next message: Steve Hall: "Re: Number of operations between BEGIN and COMMIT"
- Previous message: BP Margolin: "Re: Hiding database objects"
- In reply to: Campbell McNeill: "Field Level Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Fernando G. Guerrero" <fernan@guerrerog.org> Date: Tue, 17 Sep 2002 01:39:06 -0400
I agree with Dan that the recommended approach is to use views to restrict
access to specific columns.
As an alternative, you can assign permissions to specific columns using
Enterprise Manager (in SQL Server 2000) or the GRANT/DENY statements (SQL
7.0 and 2000):
GRANT SELECT ON Categories (CategoryID, CategoryName) TO Mary
This approach looks more flexible, but it produces a higher maintenance cost
to the database administrator, as it is necessary to track permissions on
individual columns instead of caring only about high level objects such as
views, UDFs and stored procedures.
-- Fernando G. Guerrero SQL Server MVP QA plc., UK PASS Spanish Group www.sqlserverbyexample.com www.callsql.com www.qa.com "Share what you know, learn what you don't" "Campbell McNeill" <campbell.mcneill@visionwareplc.com> wrote in message news:#Gt4GjjWCHA.3740@tkmsftngp11... > Hi, > > I need to implement a security model which restricts access down to > individual fields of data. > > The only way I can think of doing this is by using bitmasks. > > Does anyone know any other methods of doing this / anything that sql server > can do to help me achive this. > > Kind Regards, > > Campbell McNeill. > >
- Next message: Steve Hall: "Re: Number of operations between BEGIN and COMMIT"
- Previous message: BP Margolin: "Re: Hiding database objects"
- In reply to: Campbell McNeill: "Field Level Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|