March 27, 2009 at 11:42 am
Hi ,
I am planing to run Sql profiler on Production server. Just wondering does it going to impact my performence on server ?
I am running this profiler from my client machine what step I h ave to take ?
Appreciate your quick response.
Thanks
Ichbin
March 27, 2009 at 11:48 am
Profiler should never be run in production buy the developer edition and profile your code in it, cheap and zero down time.
Kind regards,
Gift Peddie
March 27, 2009 at 11:50 am
i'm running SQL profiler into production for only RPC:completed et SQL:batchcomplete for every queery more then 500 ms into my production server and is low impact into performance.
March 27, 2009 at 12:06 pm
I am running Profiler from other machine which is my desktop ..
Shall I ran the profiler ?
let me know what is best practice.
Thanks
Ichbin
March 27, 2009 at 12:09 pm
The impact on the server depends on how many events you're capturing and what kind of filters you put in place. Generally speaking traces should be configured to capture only the events you are interested in and filters should be put in place to limit the number of rows that are returned.
If you need to run the trace for a long duration I would suggest setting up a server trace that writes the trace data to a file. You can use profiler to set up the events and filters and then export the trace definition to a script that can be executed on the server. You'll have to stop the trace using sp_trace_setstatus to disable the trace when you want to review what's been captured. You could then copy the trace file to your local machine and open in profiler to do your analysis.
March 27, 2009 at 12:12 pm
Your desktop is better than production because it uses a lot of memory, you could check your resource use while you are running it.
Kind regards,
Gift Peddie
March 27, 2009 at 12:19 pm
March 27, 2009 at 12:21 pm
Hi ,
I ran the Profiler on my desktop and captured only few events. Prodcution server CPU is less then 50 % . I received errors from users they are not connecting and application servers got failed so I stopped the trace ?
Is it my trace caused the application server failed ? Please let me know your suggestion s
Thanks
Prakash Ginka
March 27, 2009 at 12:23 pm
I have told you to get a copy of developer and profile the code in a test box and yes your users error maybe related to the profiler run.
Kind regards,
Gift Peddie
March 27, 2009 at 12:32 pm
Gift Peddie (3/27/2009)
I have told you to get a copy of developer and profile the code in a test box and yes your users error maybe related to the profiler run.
No offense but that hardly helps the OP solve his problem.
ichbinraj, traces run for a short duration with a specific set of filtered events usually won't cause major problems on modern production class hardware.
Were your users seeing the same kind of problems before you started running profiler or did they happen only after you started your trace?
If you can provide more specific information about the nature of your problem and why you think you need to run profiler to solve it we'll be in a better position to help you.
March 27, 2009 at 12:38 pm
When profiler is run in production it will only profile events that will use limited resources when it is run in a test box it will be comprehensive and detailed. So most issues will be identified and code refactored. That is the reason to get a developer edition.
Kind regards,
Gift Peddie
March 27, 2009 at 12:43 pm
Hi,
We have 1 DB server and 2 apps servers
I started tracing on DB server from my desk top @ 10:50 AM but I received mail saying that they have not connecting to DB and their application server failed
then I thought My trace is taking CPU time and network time then I canceled the trace.. but still I am not understanding why does it happened
why I am running Profiler: There is one application connecting with ODBC and they are facing performance problem saying they have very slow read time from tables .. They are using only 5 tables and records as follow
A ( Records 38543)
B (Records 46873)
C (Records 110857)
D (Records 36227)
E (Records 43559)
please let me know your suggestions
Thanks
Ichbin
March 27, 2009 at 12:48 pm
di you talkin about SQL profiler or perfmon tool
March 27, 2009 at 12:53 pm
I started tracing on DB server from my desk top @ 10:50 AM but I received mail saying that they have not connecting to DB and their application server failed
then I thought My trace is taking CPU time and network time then I canceled the trace.. but still I am not understanding why does it happened
OK so to be clear the connection issues started AFTER you ran your trace and stopped once you shut the trace down, right?
why I am running Profiler: There is one application connecting with ODBC and they are facing performance problem saying they have very slow read time from tables
I would start with some basics by verifying that the indexes on the tables are not fragemented and that statistics are up to date. Did the query\queries in question run fine last week and get progressively slower over time? Do any other databases\applications make use of the server or is it dedicated to only your database and the 2 applications which you said use it?
March 27, 2009 at 1:04 pm
Hi ,
I Performed full Reindex on Database 2 weeks ago, Last night I explicitly ran the on-line index on 5 tables ..
Database is big its nearly 1 TB and used for SAP application. but these 5 tables are explicitly used by other application. based these 5 tables some other tables being synchronized .
Thanks
Ichbin
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply