Application Role and Pooled Connection Limitation

Any idea on how to overcome the limitation of not being
able to use pooled connection after application role is
enabled on a client connection to SQL Server.
Disabling Pooled connection would have a big impact in
performance, and disabling application role allows any non-
authorized application to connect to the back-end.
Of course, I could have my own code to control all this,
but it would require a big re-factoring effort. I would
appreciate if anybody has an ingenious solution to this
limitation on SQL Server.
Thanks,
Toledo>Hi Toledo,
>Since according to KB article 229564, we will encounter
problems when using
>application role with OLE DB resource pooling, if we want
to use OLE DB
>resource pooling, we cannot use application role.
>How about the following workaround?
>1. Create a SQL Server login and store the password in a
table.
>2. Only grant application role the Read right to that
table.
>3. Set application role and retrieve password.
>4. Connect using the login.
>This requires the login password to be secure so only
authroized
>application can read the password.
>
>Bill Cheng
>Microsoft Online Partner Support
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and
confers no rights.
>--Original Message--
>Any idea on how to overcome the limitation of not being
>able to use pooled connection after application role is
>enabled on a client connection to SQL Server.
>Disabling Pooled connection would have a big impact in
>performance, and disabling application role allows any
non-
>authorized application to connect to the back-end.
>Of course, I could have my own code to control all this,
>but it would require a big re-factoring effort. I would
>appreciate if anybody has an ingenious solution to this
>limitation on SQL Server.
>Thanks,
>Toledo
>.
>