Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 PERFORMANANCE ANALYSIS

Author  Topic 

sqlserverdbam
Yak Posting Veteran

54 Posts

Posted - 2008-11-04 : 13:11:59
Hi,

My company month end processing for billing system is taking longer.I want to setup somekind of trace which show me where is real problem? How can I do this? Is there any free trial version tools or any utilities available?
Please suggest.

Thanks,

spirit1
Cybernetic Yak Master

11752 Posts

Posted - 2008-11-04 : 13:15:02
check indexing and execution plans. rewrite cursors in a set based manner. those are usually the most common culprits.

_______________________________________________
Causing trouble since 1980
Blog: http://weblogs.sqlteam.com/mladenp
Speed up SSMS development: www.ssmstoolspack.com <- version 1.1 out!
Go to Top of Page

saurabhsrivastava
Posting Yak Master

216 Posts

Posted - 2008-11-04 : 15:14:36
If you are running SQl Server 2005, it has default trace in log folder. Trace file is small perhaphs help in giving you direction. If default trace is off run profiler trace to capture events.
Go to Top of Page

igorblackbelt
Constraint Violating Yak Guru

407 Posts

Posted - 2008-11-04 : 15:20:29
If this is something that your IT department is willing to invest some, I highly highly recommend a product called i3 from Precise, which is a company that Symantec bought and spin off again just recently as it didn't align with their line of business...

We use i3 daily here, it's a phenomenal tool.

Check it out:
http://www.precise.com/

I also believe Splunk has something similar, but I never worked with it.


---
http://www.ssisdude.blogspot.com/
Go to Top of Page

mcrowley
Aged Yak Warrior

771 Posts

Posted - 2008-11-04 : 15:24:34
SQL Server Profiler (included among the SQL Server tools) is generally the preferred tool to trace server activity. Run a trace of any query that has a duration of more than 500 milliseconds. If this does not turn up much, your front end may be under stress, or the front end might be getting forced to get records individually. There is a lot to look at, but Profiler is the first place to look.
Go to Top of Page
   

- Advertisement -