December 17, 2008 at 3:10 am
My Application is running very slow and it has sqlserver 2005 in backend.How to troubleshoot whether it is database related issue/OS/Network.
Thanks,
Litu
December 17, 2008 at 4:18 am
run a server-side trace on your sql server, make sure you aply appropriate filters to help you isolate what the potential issues could be.
Have a look at the result of the trace and identify any long running queries that may be causing the system to slow down. If you identify any problem queries then you will need to have a look at their execution plans and indexes to see if there is anything you can do to speed them up.
this is a very simple explanation of what steps to take, this is large topic and could involve a lot of investigation but a trace will give you a good start on where the problems lie.
December 17, 2008 at 4:19 am
You might just want to check how your other network apps are performing?
and also, have you any other databases? how are they performing?
Then'd i'd start running a trace...
Let us know how you get on.
James Howard
December 17, 2008 at 8:13 am
Thanks for your insight on this issue.I will run profiler traces on the server and let you know with my findings.
There is only one online application accessing the Database server.
Thanks,
Litu
December 18, 2008 at 2:23 am
Make sure that the clustered indexes on your tables are on monotonic fields - particularly on your larger tables. Basically, this means that inserts should generally go at the 'end' of the table - rather than be inserted potentially at any point in the table. Examples would be an identity or insert datetime column, rather than a GUID column in a web app. If you have something 'random' like a GUID then you can very rapidly run into performance issues due to the physical reordering of the table(s) escalating to table locks
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply