Re: securing 1 DB within an sqlserver.
From: Tom Moreau (tom_at_dont.spam.me.cips.ca)
Date: 11/14/05
- Next message: Dan Guzman: "Re: ACL enforcement via SP or trigger"
- Previous message: Andrew J. Kelly: "Re: Scripting Permission"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Mon, 14 Nov 2005 07:56:35 -0500
You cannot keep system administrators from accessing your database. You
have two choices (sort of). The first is to create a separate instance,
remove the BUILTIN\Administrators group and add yourself as a sysadmin.
Then, carry out administration as normal. However, there is nothing
stopping you someone from stopping the instance and copying the files
elsewhere. Here, you may be able to circumvent that by using EFS. (I'm not
sure.)
The other option is to encrypt the sensitive data itself, which you can do
if you are running SQL Server 2005.
-- Tom ---------------------------------------------------- Thomas A. Moreau, BSc, PhD, MCSE, MCDBA SQL Server MVP Columnist, SQL Server Professional Toronto, ON Canada www.pinpub.com . "Ofik" <Ofik@discussions.microsoft.com> wrote in message news:F67B11D9-D8CF-44DD-9E5D-F9BA4EABCB2F@microsoft.com... I want to install my db on an existing sql server, but I dont want every Tom *** and Harry with SQL Server Enterprise Manager to view my tables views and data. Is there a way to password protect 1 DB so that even system administrators not authorized cannot see it? Ofik
- Next message: Dan Guzman: "Re: ACL enforcement via SP or trigger"
- Previous message: Andrew J. Kelly: "Re: Scripting Permission"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]