none
WSUS Synchronization Logs Cleanup RRS feed

  • Question

  • How do you clean up years and years worth of synchronization logs?

    The Sync Log display takes forever, especially on remote sites.
    Tuesday, October 13, 2009 8:49 PM

Answers

  • The synchronization logs are maintained in a table in the WSUS database which contains all events reported to the WSUS Server. This table is automatically maintained (presuming you're using WSUS v3).

    Looking at the sync log report from a remote site may well take some time to render, since you're moving howEverMany megabytes of log entries across a slow-speed wire.

    One thing that can help, however, is reindexing the WSUS database. See Appendix I (http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx) of the WSUS Operations Guide for information on performing WSUS database maintenance.

    Other optimization techniques you might use are:

    - Separate the WSUS database and WSUS Content store on separate logical volumes, so as to minimize disk fragmentation of the database if/when it auto-grows, and regularly defragment the content store volume to ensure contiguous access to clusters containing files being downloaded by clients, and minimizing the occurrence of fragmentation when files are written to the store after being downloaded from MU.

    - Separate the WSUS database and WSUS Content store on separate physical volumes, so as to minimize contention for disk i/o bandwidth -- which will result in faster response times from queries performed against the WSUS database, and faster downloads for client systems.

    - Prior to running the database maintenance documented in Appendix I of the OpsGuide, defragment the volume containing the WSUS database.

    - Regularly run the WSUS Server Cleanup Wizard, so as to minimize the number of records stored in the updates table and increase performance of scanning times by removing updates that are no longer relevant.

    - Do not store WSUS Content on the SYSVOL, so as to avoid the possibility of overfilling the SYSVOL (and causing all sorts of unwanted havoc).

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, October 13, 2009 10:48 PM
    Moderator

All replies

  • The synchronization logs are maintained in a table in the WSUS database which contains all events reported to the WSUS Server. This table is automatically maintained (presuming you're using WSUS v3).

    Looking at the sync log report from a remote site may well take some time to render, since you're moving howEverMany megabytes of log entries across a slow-speed wire.

    One thing that can help, however, is reindexing the WSUS database. See Appendix I (http://technet.microsoft.com/en-us/library/dd939795(WS.10).aspx) of the WSUS Operations Guide for information on performing WSUS database maintenance.

    Other optimization techniques you might use are:

    - Separate the WSUS database and WSUS Content store on separate logical volumes, so as to minimize disk fragmentation of the database if/when it auto-grows, and regularly defragment the content store volume to ensure contiguous access to clusters containing files being downloaded by clients, and minimizing the occurrence of fragmentation when files are written to the store after being downloaded from MU.

    - Separate the WSUS database and WSUS Content store on separate physical volumes, so as to minimize contention for disk i/o bandwidth -- which will result in faster response times from queries performed against the WSUS database, and faster downloads for client systems.

    - Prior to running the database maintenance documented in Appendix I of the OpsGuide, defragment the volume containing the WSUS database.

    - Regularly run the WSUS Server Cleanup Wizard, so as to minimize the number of records stored in the updates table and increase performance of scanning times by removing updates that are no longer relevant.

    - Do not store WSUS Content on the SYSVOL, so as to avoid the possibility of overfilling the SYSVOL (and causing all sorts of unwanted havoc).

    Lawrence Garvin, M.S., MCITP:EA, MCDBA
    Principal/CTO, Onsite Technology Solutions, Houston, Texas
    Microsoft MVP - Software Distribution (2005-2009)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    My Blog: http://onsitechsolutions.spaces.live.com
    Tuesday, October 13, 2009 10:48 PM
    Moderator
  • Hi,

    I want to see if the information Lawrence provided was helpful. Please keep us posted on your progress and let us know if you have any additional questions or concerns.

    We are looking forward to your response.

    Thanks
    • Proposed as answer by kjd0993 Friday, September 15, 2017 6:22 PM
    Thursday, October 22, 2009 6:23 AM
    Moderator
  • All the optimization techniques did not really help for me. Showing the synchronization log was still slow.
    If you do not need the reported events data, you can delete it with the SQL command "truncate table dbo.tbEventInstance".
    I do not need to say that this will be unsupported and that this command will delete data! I did export the data before truncating the table to remain the informations.

    Best regards
    Clemens
    Tuesday, January 26, 2010 7:45 AM