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.
  • 0

    Server disk resources are pretty flatlined for the whole time so think I'll get it logged with Sophos.  Thanks for all your help.

    :21487
  • 0

    Hi,

    It sounds like it's at least part of the issue if not the issue.  Although I'm suprised the durations in SQL didn't reflect the poor I/O.  Anyway, I would suggest, drop the unused databases, leaving just the SOPHOS50 and SOPHOSPATCH.


    Maybe you can move the SOPHOS50 and SOPHOSPATCH MDFs at least (ideally the LDFs also) to a different drive? The KBA: http://support.microsoft.com/kb/818565 should help with the basics of what to do there.  Ideally it's best to put the LDF and MDF of a database on different drives to speed up data access and not on the same drive as the OS.  This may or maynot be possible without adding drives but maybe you have this ability.

    You could always setup a database maintenance plan also.

    http://msdn.microsoft.com/en-us/library/ms189953.aspx

    This can be done in SQL Server Management Studio.  There are plenty of guides searching Google for

    Creating a SQL maintenance plan

    That should keep things healthy.


    Regards,

    Jak 

    :21501
  • 0

    Managed to resolve my issue in the end.

    - Purged autoupdate error data that was over 100days old from the database (which brought it down from over 100,000 records to 30,000)

    - Re-built some of the table indexs as they were quite heavily fragmented

    - And performed a database shrink which took the DB down from 414mb to 118mb.  Gave the server a reboot and computer data now appears almost instantly

    :21731
  • 0

    Glad it's all running a bit smoother!

    Jak

    :21743