RE: Securing a SQL Server Database
- From: weilu@xxxxxxxxxxxxxxxxxxxx (Wei Lu [MSFT])
- Date: Mon, 18 Dec 2006 06:58:42 GMT
Hello Greg,
Since the SA is the system administrator of the sql server, you could not
avoid it to access the datbase.
Although you could disable the sql authentication in the server to avoid
the SA account to use, this will effect other users in the same database
server. Also, if some login is assigned as sysadmin role in the sql server,
it could access all the database on that server.
The database file in the sql server is not just a file but it will be
managed by the sql server services. So the system admin need to monitor all
the databases on that server. This makes sense. My suggestion is that you
need to control your system admin account and did not grant other users to
such high level permission.
As for the encrypt the database file, I suggest you to grant a SYMMETRIC
KEY for the database so that only the user who have the key could copy and
open the database file in the sql server.
For more detailed information, you could refer following articles:
GRANT Symmetric Key Permissions (Transact-SQL)
http://msdn2.microsoft.com/en-us/library/ms179887.aspx
Security Considerations for SQL Server
http://msdn2.microsoft.com/en-us/library/ms161948.aspx
Hope this will be helpful for you to understand the security in SQL Server.
Sincerely yours,
Wei Lu
Microsoft Online Partner Support
=====================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix
issues and simple how to questions.
We also love to hear your product feedback!
Let us know what you think by posting
- from the web interface: Partner Feedback
- from your newsreader: microsoft.private.directaccess.partnerfeedback.
We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others
may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================
.
- Prev by Date: Re: Securing a SQL Server Database
- Next by Date: Re: Don't want Trusted Connection option...
- Previous by thread: Re: Securing a SQL Server Database
- Next by thread: Re: Securing a SQL Server Database
- Index(es):
Relevant Pages
|
|