«
»

WSUS V3 and connections to it’s internal database

10. May, 2007

Have you ever wanted to connect to the “Windows Internal” database that WSUS V3 uses?

While “Windows Internal Database” is Microsoft SQL Server 2005 in a limited edition (just like MSDE, WMSDE before it), the familiar access tools to the DB went missing, and connecting using standard ways doesn’t work either.

It doesn’t work right out of the box. First, you need SQL Management Studio Express.

Install and start it. Specify the following connection string:

\\.\pipe\mssql$microsoft##ssee\sql\query

Please note that, as implied by the connection string, this connection only works locally.

Category: Windows  |  Comment (RSS)  |  Trackback

8 Comments

  1. Connecting to the WSUS database with SQL 2005's tools - E-Bitz - SBS MVP the Official Blog of the SBS "Diva":

    [...] http://projectdream.org/wordpress/2007/05/10/wsus-v3-and-connections-to-its-internal-database/ [...]

    12. June, 2007, 23:40

  2. BruceK:

    Hi, any idea how to connect to the wsus v3 windows internal database from vbscript? Here’s what used to work with MSDE:

    Set objConnection = CreateObject(“ADODB.Connection”)
    objConnection.ConnectionTimeout = 25
    objConnection.Provider = “SQLOLEDB”
    objConnection.Properties(“Data Source”).Value = strComputerName &
    “\WSUS”
    objConnection.Properties(“Integrated Security”).Value = “SSPI”

    thanks,
    Bruce

    8. September, 2007, 11:06

  3. Leo:

    I am also looking to setup a vb script to connect…. any help on how to setup the connection would be appreciated…

    I have tried every which way I can think of… here is the latest “try” that also did not work.

    dbConn = “Provider=SQLOLEDB;” & _
    “Data Source=localhost;” & _
    “Initial Catalog=SUSDB;” & _
    “Data Source=127.0.0.1\pipe\MSSQL$MICROSOFT##SSEE\sql\query;” & _
    “Integrated Security=SSPI” & _
    “Persist Security Info=False” & _
    “Network Library=dbnmpntw”

    set objDBConnection = createobject(“adodb.connection”)
    objDBConnection.Open dbConn

    4. October, 2007, 22:48

  4. Tancque:

    Try this:
    dbConn = “Provider=SQLNCLI;” & _
    “Data Source=\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query;Database=SUSDB;Trusted_Connection=yes”

    It uses the native client instead of OLE.

    Good Luck.
    Tancque

    31. October, 2007, 16:22

  5. SBS - 2k8 knapper Hauptspeicher - MCSEboard.de MCSE Forum:

    [...] [...]

    5. May, 2009, 12:21

  6. dave:

    This connectionstring works for me “Provider=Sqloledb;Data Source=\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query;Database=SUSDB;Trusted_Connection=yes”

    11. August, 2009, 16:58

  7. MikeH:

    Thanks! This little gem is invaluable.

    What’s strange, though, is that the SQL Server Management Studio Express console will open the WSUS database directly (WHIRLWIND\MICROSOFT##SSEE) on Windows SBS 2003, but requires your bit of brilliance on Windows Server 2003 Standard.

    10. July, 2010, 22:40

  8. DBA:

    I’ve Found a SQL scanner that can locate any SQL server at your network (multi-subnet) it can also try to brute force the SA user account (or any other account) to make sure the password is not easy.
    you can get it here: http://www.softpedia.com/get/Internet/Servers/Database-Utils/SQL-Locator.shtml

    29. July, 2010, 16:01

Leave a comment