Re: Securing Data
- From: "Bruce Martin" <bmartin@xxxxxxxx>
- Date: Tue, 28 Feb 2006 06:59:49 -0500
Thanks Tom, that's the path I'm going to take.
Bruce
"Tom Moreau" <tom@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eV$%23xj8OGHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
You can secure it any way you like. I'd go with the one DB and simply
grant
as required. By default, non-DBO's have no access anyway.
--
Tom
----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"Bruce Martin" <bmartin@xxxxxxxx> wrote in message
news:u%23xisT8OGHA.3944@xxxxxxxxxxxxxxxxxxxxxxx
I got the job of DBA handed to me since I talk DB2 on mainframes. Anyway
we
have a SQL2K with maybe 12-14 users, using WinNT auth. to log on. We are
going to getting some data that only certain folks can see. We have 2
restricted tables in one of our databases right now and access is
controlled
by denying access to certain users. I have suggested that we should
created
a secured data base and only allow the cleared folks to access it. Is this
the best way to attack this problem, or should we do something else.
Thanks guys/gals
Bruce
.
- References:
- Securing Data
- From: Bruce Martin
- Re: Securing Data
- From: Tom Moreau
- Securing Data
- Prev by Date: Re: Adding permissions to an AD user on a remote database
- Next by Date: Re: xp_cmdshell without proxy acoount
- Previous by thread: Re: Securing Data
- Next by thread: Re: Change service account with SQL server 2000 sp4
- Index(es):
Relevant Pages
|
|