Setting up and Configuring WSUS to use SQL database instead of WID

Set up your WSUS to use SQL database instead of WID.

 General   December 2, 2021

Setting up and Configuring WSUS to use SQL database instead of WID


WID and SQL database which one is preferable?

It all depends on the number of computers in view, SQL server will provide more stability than WID for larger number of computers.


If you envision to use maybe around 100 or less computers, then WID will get the job done for you. But anything more than that, then its ideal to setup and SQL server to avoid several hangings and crashes during wsus usage.


Which SQL Server do I need?

To setup WSUS you don’t need a full-blown SQL server with all the bells and whistles.

Here we are going to setup WSUS with SQL 2014 Express Localdb, The Localdb is a lightweight option of the SQL Server that allows you setup a local database without the heavy weight load, you can read more about it here:::::


Setting Up the LocalDb.

Go ahead and download the localdb here choose Localdb for your Arch and continue



After downloading it, install it with the default options. Now all we need from this localdb is just a database instance our WSUS can connect to and manage or data.


After installation, open an elevated command prompt and follow the below steps.


To check information regarding your Localdb and all instances

  SqlLocalDb info  



This means the Localdb has 3 instances as listed above.


To view more info about each instance

  SQLLocalDB info v12.0  



To create a new instance which is what we would want to do for our WSUS

  SqlLocalDB create WSUS  

  "C:\Program Files\Microsoft SQL Server\120\Tools\Binn\SqlLocalDB.exe" create "v12.0" 12.0 -s  


To check status of the newly created instance

  SqlLocalDB status WSUS  

We will notice it will be in a stopped state.


To start the new instance

  SqlLocalDB start WSUS  


View the status again and copy the instance Pipe Name, this is what we will feed in our SQL connection string box in the SQL connection installation on server manager.

The box says server\sqlinstance. But just enter the whole Instance pipename


The Instance Pipe name is still what you need as the server if you are connecting to the database via management console.





That’s all, install your WSUS and SQL connector with the Instance Pipe Name you just created.


For More SQL server LocalDB Management codes Check this out, and this and this, and this, and this.

Copyright © 2022 John & Cyber Security . All Right Reserved.