In a lot of applications where a web server is talking to a data base three is nothing in the query that indicates who the web user is. That is, the web server maintains the user context and uses a single privileged user for queries.unless you can see something in the query, you probably are not going to be able to do this.
On Jun 23, 2011 9:26 PM, "akshay vashishtha" <
akshay123_vashishtha@xxxxxxxxx> wrote:
> Hi Everyone,
>
> I did not mention the actual problem in the subject line as it would not have been very clear if i would have written it there. :) Ok..Let me tell you the problem.
>
> I'm doing a capture on the web server. The web server contacts the SQL server for getting the data. Now, there are many ports (say 10 - ports ranging from 4001 to 4010) on web server which contacted the SQL server on port 3180 (used for SQL transactions) in my capture.
> There is a behavior called 'tcp piplelining' which happens between the Web and SQL server. Let me explain you what i'm trying to say. As there are many users who are accessing the website, the data of many users (say 5 users) are going through the same port (say port no 4001) from web server to the sql server. Similarly for all other ports. So, while troubleshooting I'm not able to differentiate my traffic which my system generated.One solution is to do capture in a single user window.
> Is there any other tool which can show my data separately i.e. do not mix it with the data of other users??
>
> Regards,
> Akshay
