Re: SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous - can I control this?
- From: alex_wh@xxxxxxx
- Date: Thu, 14 Aug 2008 00:03:13 -0700 (PDT)
On 13 авг, 17:59, "Bob Barrows [MVP]" <reb01...@xxxxxxxxxxxxxxx>
wrote:
I'm not sure I completely understand your description, but it seems that youI am sorry I don't wrote it in the first post, I use MS SQL 2000
are misusing CONTEXT_INFO, which is intended to allow multiple batches to be
run on the same connection in order to facilitate the new MARS
functionality, not to allow multiple users to use the same user info. It
sounds as if you should be using the new "EXECUTE AS user" functionality to
accomplish your goal.
server, there is no EXECUTE AS functionality, and because I never know
about ADO internal connection pooling, our own server login procedure
stores user ID in context_info server storage to share the same user
context between all server procedures after our own user login. We
have many reasons to implement our own login procedure and we will use
it. I can use another storage for sharing user context info but what
is this storage?
I need to mark all connections (and their activities) that ADO creates
under the hood with the same tag on the server side from arbitrary
moment -- I named it as "our internal server login procedure".
First time @@SPID and dedicated table (master.dbo.sysprocesses with
context_info field) was good but ADO internal connection pooling is
bad because I want to execute parallel tasks in my application. And I
need to keep this mark on the server side, not as parameter in every
call to any of our security-depended server procedures.
I'll be glad to hear any succestions.
.
- Follow-Ups:
- References:
- SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous — can I control this?
- From: alex_wh
- Re: SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous - can I control this?
- From: Bob Barrows [MVP]
- SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous — can I control this?
- Prev by Date: Re: SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous - can I control this?
- Next by Date: Re: SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous - can I control this?
- Previous by thread: Re: SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous - can I control this?
- Next by thread: Re: SQLOLEDB provider internally creates multiple connections to SQL server when commands executed asynchronous - can I control this?
- Index(es):
Relevant Pages
|
