sql server connect: sql database security -- sql server connect

Re: sql database security

Min
6/30/2005 6:31:01 PM

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

[quoted text, click to view]

Re: sql database security

Kevin3NF
7/1/2005 8:27:37 AM

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

[quoted text, click to view]

Re: sql database security

bahados
7/1/2005 4:11:03 PM

Why would the someone that is not in the SA role try to block access to a
database. This sounds like you are trying to get around the IT department
and you don't have the proper permissions. That is exactly why you can't do
that in SQL Server.
--
bahados

[quoted text, click to view]

Re: sql database security

Min
7/3/2005 8:17:01 PM

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

[quoted text, click to view]

Re: sql database security

Mike Epprecht (SQL MVP)
7/4/2005 12:00:00 AM

Hi

"Embedded SQL" is a way to access SQL Server 7.0 and below from DOS or 16
bit applications. It is not a server install.

If you look at prior threads in the newsgroups, this issue has been raised
before.
An administrator will always have access to your DB.
Don't lock your own users out of the DB as then may need to restore and back
it up.
If you have Trade Secrets/Business Logic that needs to be kept safe, do it
in the application middle tier.
Protect yourself though licensing, not obscure security.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

[quoted text, click to view]

Re: sql database security

Min
7/4/2005 1:17:02 AM

To all who replied to my question:

Thank you very much for your time and advice.
Most importantly, thanks for convincing me to give up trying this idea
totally.

Min

[quoted text, click to view]

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the sql server connect group.