Re: db_denydatawriter
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Fri, 19 Oct 2007 21:50:50 +0000 (UTC)
Ant (Ant@xxxxxxxxxxxxxxxxxxxxxxxxx) writes:
I'm wondering. We have an application which uses its own login to interact
with this database. If a user has read write access for this application,
perhaps this also gives read write access on the database to this user?
Sounds dangerous but this might be what is happening perhaps?
No, the fact that a user has permission to run a certain Windows
executable, does not give her any permissions in SQL Server.
Did you check through Query Analyzer who she is really logged in as
when she use Enterprise Manager? Can she run UPDATE statements in QA
when logged in as herself?
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- Re: db_denydatawriter
- From: Uri Dimant
- Re: db_denydatawriter
- From: Ekrem Önsoy
- Re: db_denydatawriter
- From: Ant
- Re: db_denydatawriter
- Prev by Date: Re: what is the best way to store passwords and credit card information in SQL Server 2005?
- Next by Date: Re: db_denydatawriter
- Previous by thread: Re: db_denydatawriter
- Next by thread: Re: db_denydatawriter
- Index(es):
Relevant Pages
|
|