Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 14 replies
  • Subscribers 1 subscriber
  • Views 6316 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Slow SEC 5 response

CDC

I've found since upgrading to SEC5 the console is very slow when clicking on a computer in the status view in order to view its details.  The screen will come up blank and then just over 2mins later the details finally appear.

Anyone else have this?  I'm not sure if this is a common problem as I had a quick search through the forum but couldn't find any posts on the issue.

:21043


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    Do you have SQL Profiler installed on the database machine?

    As the data displayed in the computer details window is the result of a number of queries, I would try and identify which component is taking the time.  Monitoring the "Duration" of the various component queries in SQL Profiler will tell you which tables perhaps should be purged?

    For example, when opening the details of a computer I see the following query of many taking place:

    exec dbo.ErrorHistoryListGet '2012-01-20 21:28:31',N'1,',N'SAV,'

    which is providing the computer details window with the SAV error history for machine with ID = 1.  I.e. the machine's computer details I opened.  What is the duration of this query for you?  note, they are in milliseconds.

    Other queries that are part of the query are:

    exec dbo.ErrorAlertOutstandingIDListGet N'1,',N'SCF,',100

    exec dbo.ErrorAlertOutstandingIDListGet N'1,',N'ALC,',100

    exec dbo.ErrorAlertOutstandingIDListGet N'1,',N'SEA,',100

    There are quite a few more but you will see them all in SQL Profiler.

    The "Duration" column is the key here to pinning down where the delay is coming from.


    Regards,

    Jak

    P.S. If you don't have SQL Profiler (You need full SQL Server rather than just SSMS), there is another way to get the information out of SQL and that is to turn on C2 Level Auditing in SQL comination with running "fn_trace_gettable" queries against the trace file: http://msdn.microsoft.com/en-us/library/ms188425.aspx .  A bit clunky and will slow down the SQL server to some degree but it will work also, you can also use clauses against the duration column to narrow down results.  Even if you have SQL Profiler you can save the Profiler trace and perform the same queries against the trace if that's easier than using the GUI of Profiler.  

    The other option and possibly simpler is free SQL Profiler like tools; you can find them by searchin on Google.

    :21125
Reply
  • 0

    Hi,

    Do you have SQL Profiler installed on the database machine?

    As the data displayed in the computer details window is the result of a number of queries, I would try and identify which component is taking the time.  Monitoring the "Duration" of the various component queries in SQL Profiler will tell you which tables perhaps should be purged?

    For example, when opening the details of a computer I see the following query of many taking place:

    exec dbo.ErrorHistoryListGet '2012-01-20 21:28:31',N'1,',N'SAV,'

    which is providing the computer details window with the SAV error history for machine with ID = 1.  I.e. the machine's computer details I opened.  What is the duration of this query for you?  note, they are in milliseconds.

    Other queries that are part of the query are:

    exec dbo.ErrorAlertOutstandingIDListGet N'1,',N'SCF,',100

    exec dbo.ErrorAlertOutstandingIDListGet N'1,',N'ALC,',100

    exec dbo.ErrorAlertOutstandingIDListGet N'1,',N'SEA,',100

    There are quite a few more but you will see them all in SQL Profiler.

    The "Duration" column is the key here to pinning down where the delay is coming from.


    Regards,

    Jak

    P.S. If you don't have SQL Profiler (You need full SQL Server rather than just SSMS), there is another way to get the information out of SQL and that is to turn on C2 Level Auditing in SQL comination with running "fn_trace_gettable" queries against the trace file: http://msdn.microsoft.com/en-us/library/ms188425.aspx .  A bit clunky and will slow down the SQL server to some degree but it will work also, you can also use clauses against the duration column to narrow down results.  Even if you have SQL Profiler you can save the Profiler trace and perform the same queries against the trace if that's easier than using the GUI of Profiler.  

    The other option and possibly simpler is free SQL Profiler like tools; you can find them by searchin on Google.

    :21125
Children
No Data