Re: sql database security

Tech-Archive recommends: Speed Up your PC by fixing your registry

Thanks for the information.
1. Putting it on a different "server" means putting the database on a
different pc?
That doesn't solve my problem since the sa of that pc still can access the
database, right?

2. Is there any other solution to ONLY allow my application to open the
database and not any other personnel? Do I have to revert to sybase in this
case?

Min


"Kevin3NF" wrote:

> You cannot lock the sa (or any user in the sysadmin server role) out of
> seeing a database by any method other than putting it on a different server.
>
> --
> Kevin Hill
> President
> 3NF Consulting
>
> www.3nf-inc.com/NewsGroups.htm
>
> www.DallasDBAs.com/forum - new DB forum for Dallas/Ft. Worth area DBAs.
>
> www.experts-exchange.com - experts compete for points to answer your
> questions
>
>
> "Min" <limsohmin@xxxxxxxxxxx> wrote in message
> news:8119E780-4015-45B0-BA34-E32A958072FD@xxxxxxxxxxxxxxxx
> > This is the first time I use SQL server for my application.
> > I need to set up 2 databases in the same server.
> >
> > 1. The first database need to be "hidden" hence no one else even SA should
> > not be able to see the database except for my application.
> >
> > 2. The second database can be seen by SA
> >
> > Is this possible on SQL Server?
> >
> > Pls enlighten me as I have been trying various setting but in vain!
> > Min
> > ps: I think this can be done easily using sybase ASA. I just simply set
> > the
> > username and password.
> >
>
>
>
.

Relevant Pages