Security - Lock Database
- From: "Greg" <gjsetnes@xxxxxxxxxxx>
- Date: Sat, 26 Jan 2008 23:11:12 -0800
I want to make some changes regarding accessing my SQL Server Database, but
before I start playing around with it, I want to post something to see if
anyone can give me some guidence so I don't end up locking myself out of my
SQL Server Database or SQL Server all together.
At my office, you are required to use SQL Server Authentication to login to
the SQL Server, which is what I want to achieve at a minimum. What steps
should I take to lock down my SQL Server so that it requires an SQL User
Account and Password to login?
Also, I've asked this in a previous post I think, but its not longer
available. On top of locking down SQL Server as a whole, I'd also like to
lock down my specific database as well. Is it possible to provide an SQ
(System Administrator) type user account that has access to everything,
except a specific database? From what I recalled in the past, it was not
possible to restrict an SA type user from being able to delete a database.
Ultimately, what I am looking to achieve. I want my customers to have full
access to their SQL Servers, but I don't want anyone to be able to browse
the structure of my database, if not authorized. Not that my database
structure would give away much, I'd just like to protect it from prying
eyes.
Thanks.
.
- Follow-Ups:
- Re: Security - Lock Database
- From: Erland Sommarskog
- Re: Security - Lock Database
- From: Ekrem Önsoy
- Re: Security - Lock Database
- From: Uri Dimant
- Re: Security - Lock Database
- Prev by Date: Re: Can't login to SQL Server
- Next by Date: Re: Security - Lock Database
- Previous by thread: Re: SQL Server 2005 security question
- Next by thread: Re: Security - Lock Database
- Index(es):
Relevant Pages
|