Well , then you will have to build a logic in the second tier of application
(where you keep the pass) to check it againts SQL Server and return the
message
This example determines whether the current user can grant the INSERT
permission on the authors table to another user.
IF PERMISSIONS(OBJECT_ID('authors'))&0x80000=0x80000
PRINT 'INSERT on authors is grantable.'
ELSE
PRINT 'You may not GRANT INSERT permissions on authors.'
"Pure Heart" <PureHeart.TakeThisOut@discussions.microsoft.com> wrote in message
news:35FC0D5D-65AB-41F3-A5DB-DC79E84EA1E7@microsoft.com...
> hi
>
> thanks for the replay but its away from my question i was asking about
> security implemented in a .NET application
> --
> Ammar S. Mitoori
> IT Head QIMCO Co.
> Tel : +9744831199
> Mobile : +9745378400
> Fax : +9744831643
>
>
> "Uri Dimant" wrote:
>
>> Pure
>>
>> ttp://vyaskn.tripod.com/sql_server_security_best_practices.htm --------security
>> best practices
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> "Pure Heart" <PureHeart.TakeThisOut@discussions.microsoft.com> wrote in message
>> news:5CE06A84-A5AE-48A1-BAA4-47B844FC2C29@microsoft.com...
>> >
>> > Hi
>> >
>> > i was wondering instead of implementing my own security schema inside
>> > my
>> > application code is it recommended to depend on SQL Security so a user
>> > will
>> > connect with user name and password and if he dont have a permission on
>> > SQL
>> > to delete or update he will egt an message i feel its more simple what
>> > you
>> > think ?
>> >
>> > thank you
>> > --
>> > Ammar S. Mitoori
>> > IT Head QIMCO Co.
>> > Tel : +9744831199
>> > Mobile : +9745378400
>> > Fax : +9744831643
>>
>>
>> >> Stay informed about: Application Security based on SQL Security