locked
2012R2 Wsus with SQL server Express. RRS feed

  • Question

  • Hello,

    Im planing the installation of WSUS 2012R2 and SQL server express. I know the 10gb limitation of the DB, i dont think our DB exceeds 3 or 4GB.

    On my company they prefer to use SQL Express instead WID. 

    In the future, we will migrate the SQL express to SQL 2014 or 2016, when we buy it.

    Is this a good action plan ? 

    Many thanks ;)

    Wednesday, December 4, 2019 9:01 AM

All replies

  • Hi Pedro,

    As per my experience, the 10 GB limitation will affect.

    If you are going to buy licence version of SQL, Then it's OK at this time.

    https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/plan/plan-your-wsus-deployment

    Wednesday, December 4, 2019 9:20 AM
  • Hi Pedro,

    The plan sounds OK to me, make sure to double check the supported SQL Server versions and editions before migrating your WSUS database.

    WSUS database requirements
    https://docs.microsoft.com/en-us/windows-server/administration/windows-server-update-services/plan/plan-your-wsus-deployment#wsus-database-requirements

    Also make sure to back up your database prior to the migration.

    When you migrate from SQL Server Express to either Standard or Enterprise, make sure to check that the new SQL Server is licensed (How to license SQL Server).

    Best regards,
    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, December 4, 2019 9:28 AM
  • Hi Pedro

    You can upgrade SQL Server Express to SQL Server 2014 or 2016..

    Wednesday, December 4, 2019 10:04 AM
  • Thanks to all.

    Bhupen, the SQL server will be another server dedicated to only database. Actually we have WSUS 2008R2 and SQL 2005, which is not compatible with Wsus 2012.

    The plan is migrate the local SQL express DB to the new server SQL 2014/2016 when available.

    Regards 

    Wednesday, December 4, 2019 10:21 AM
  • The plan is migrate the local SQL express DB to the new server SQL 2014/2016 when available.

    It is okay.
    Please refer to Microsoft article, this provides a complete set of migration steps: "Migrate WSUS".
      

    Regards,
    Yic


    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, December 5, 2019 7:10 AM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, December 13, 2019 5:41 AM
  • While your situation would work (SQL Express and then migrate to SQL Standard), unless you have a need for remote requirements (from other systems monitoring the SUSDB database), I'd still recommend using the WID. I don't see a real reason not to use it. https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-1-choosing-your-server-os/ and you can still use SSMS to connect to the WID.

    Unless you're actually needing to purchase a SQL Standard license for other reasons, there's no issues keeping the WID. Just make sure you're doing the maintenance on it. How often should you be doing WSUS maintenance?


    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Monday, December 16, 2019 12:15 AM
  • I've had WSUS running on the same install since 2014, managing over 90 client systems and over 20 servers. It has been upgraded using in-place upgrade measures from 2012 to 2012R2 and then to 2019. I'm using the WID. I am also using WSUS Automated Maintenance (WAM) © (full disclosure, WAM is our product).

    Adam Marshall, MCSE: Security
    https://www.ajtek.ca
    Microsoft MVP - Windows and Devices for IT

    Monday, December 16, 2019 12:17 AM
  • Hi Everyone,
       

    Since this thread has not been updated for a long time, the following thread summary is provided for reference during subsequent follow-up.
      

    • Issue Symptom
      Consultation on WSUS database migration from SQL 2005 to SQL 2014/2016
         
    • Possible Cause
      Counseling
        
    • Troubleshooting Steps so far
      Operational procedures have been provided.
        
    • Next Step
      Waiting for reply.
          
    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, December 20, 2019 7:28 AM