May 14, 2003 at 7:02 am
You have to first connect to the db, using either trusted or sql login, then execute the approle proc. That turns off permissions associated with the original login as far as the app is concerned. Downside is that you have to execute the proc on every single connection the app opens.
Andy
May 14, 2003 at 7:44 am
The app role binds to the connection itself. This means if you're doing things like Resource Pooling with OLE DB, the app role is in effect, even if your application successfully initiated its own close connection and open connection. With Resource Pooling, the connection will be held open in the event that it can be reused.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
http://www.netimpress.com/shop/product.asp?ProductID=NI-SQL1
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply