October 30, 2013 at 5:09 pm
Hi, I have spent a lot of time recently trying to track down why we have experienced series performance spikes on our SQL server that are causing major issues for users. The issue is related to a 3rd party package so there is not much we can do to change things, but I am hoping to go back to the vendor with the profiler details. My question is more about identifying what user is causing the specific spikes. Because the application uses a generic name to connect to the database I cannot use the LOGINNAME, as each connection is the same and because our users are connected via Citrix using a common desktop the HOSTNAME is the Citrix server not the user workstation. Is there any other way within SQL to be able to identify the individual user (I suspect the answer is "no").
thanks
Brad
October 31, 2013 at 3:54 am
As you suspected, the answer is no.
Does the application perform some kind of logging? Maybe you can find something in there.
-- Gianluca Sartori
October 31, 2013 at 4:21 pm
No worries, I suspected that would be the answer.:-)
November 1, 2013 at 1:52 pm
Not that familiar with Citrix, but maybe there is some way to get it to pass the original login info? Perhaps as some type of comment, or by writing it to a table, or using CONTEXT_INFO()?! You just think there has to be some way of getting more info :-).
SQL DBA,SQL Server MVP(07, 08, 09) "It's a dog-eat-dog world, and I'm wearing Milk-Bone underwear." "Norm", on "Cheers". Also from "Cheers", from "Carla": "You need to know 3 things about Tortelli men: Tortelli men draw women like flies; Tortelli men treat women like flies; Tortelli men's brains are in their flies".
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply