WSUS on the front end with SQL 2005 on the back end

Discussion in 'Update Services' started by John, May 12, 2006.

  1. John

    John Guest

    Hello all,

    I will be implementing WSUS soon. Then migrating from SUS to WSUS on
    separate servers. In a few months after I migrate from SUS to WSUS, I may
    need to move WSUS content from my backend SQL server to another SQL backend
    server to do the SQL upgrade from 2000 SP3 to 2005 on the original backend
    SQL server.
    I have a couple questions:
    1) Are there any issues w/ WSUS using SQL 2005 on the backend?
    2) Since WSUS content will be stored temporarily on the other SQL server
    (also 2000 SP3), will there be any issues?
    3) Which method will be the best to temporarily move my WSUS content
    temporarily? I'd assume the cmd line movecontect. (?)

    Any advice is appreciated.
    John, May 12, 2006
    1. Advertisements

  2. John

    Dave Mills Guest

    But the rumblings are that SQL 2005 will be supported soon so in a few month
    time when you want to use SQL 2005 you may fad it supported. I have no insider
    info but hear the rumbling in the group.
    Dave Mills, May 12, 2006
    1. Advertisements

  3. John

    Nick Payne Guest

    I have several WSUS servers using SQL2005 for the database...

    BTW, the database just stores metadata, not the content. If you copy the
    WSUSContent directory to another server and then install WSUS on that server
    using a different database but specifying the same dir for storing the
    content, then the existing content will be used when you approve updates.
    Nick Payne, May 12, 2006
  4. John

    John Guest


    This is great info. Thanks Mohammed. I appreciate all the replies.
    John, May 13, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.