Re: sql database security
- From: Min <limsohmin@xxxxxxxxxxx>
- Date: Sun, 3 Jul 2005 20:17:01 -0700
I wanted a database that is hidden such that ONLY my application can access
by supplying an ID and password. No one else can access it unless he has my
ID and password.
WHAT ABOUT EMBEDDED SQL?
I just read about embedded sql. It seemed that this will allow application
to be installed in end-users' environment together with database without any
system administrator. Is this true?
And under Login Security Options:
It says: "Standard Security" is SQL server's default login security mode. I
think it uses SQL server's own login validation process for all connections.
It has no coordination with Windows NT accounts or passwords. Each SQL
server user connection must provide a valid login ID and password when it
connects to the SQL server. So I need not let my users know the ID and
password (need to prevent them from accessing my database) and my application
still runs. Is this ever possible?
Please enlighten me! It is really appreciated.
Thanks.
Soh Min
"Kevin3NF" wrote:
> Someone else may step in, but I am not aware of any way to lock sa out of a
> database. SA is part of the sysadmin server role and cannot be removed.
> The sysadmin server role had rights to do anything in the installation and
> cannot be changed to the best of my knowledge.
>
> Yes, I was referring to having a different server, either on a different box
> or on a different instance on the same box
>
> --
> 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:668942E3-7E14-4E20-99DA-A00FF9C4C607@xxxxxxxxxxxxxxxx
> > 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.
> >> >
> >>
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: sql database security
- From: Mike Epprecht \(SQL MVP\)
- Re: sql database security
- References:
- Re: sql database security
- From: Min
- Re: sql database security
- From: Kevin3NF
- Re: sql database security
- Prev by Date: SQL Server 2000 for Small Business Server 2003
- Next by Date: Re: sql database security
- Previous by thread: Re: sql database security
- Next by thread: Re: sql database security
- Index(es):
Relevant Pages
|