James, You can connect to the WID using SQL management studio, but your connection strings are not intuitive. Here is a blog post for a different MS tool that uses a WID, process is the same for the WSUS DB.
https://blogs.msdn.microsoft.com/vedvyas/2014/08/19/following-is-the-steps-to-connect-to-these-windows-internal-database-on-windows-2012-machine-this-to-access-the-wap-configuration-from-the-adfs-configuration-database/ "For server name enter \\.\pipe\MICROSOFT##WID\tsql\query in case if we are connecting to Windows Server 2012 internal database. If we are connecting to windows 2003 and 2008 windows internal DB then we use \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query" On Tue, Sep 27, 2016 at 3:37 PM, Beardsley, James < [email protected]> wrote: > https://support.microsoft.com/en-us/kb/3194588 > > > > As I’m sure you all know, MS posted this KB article about how to resolve > the 0xc1800118 error when deploying 1607. The resolution instructions are > quite involved but one of the things mentioned is to run some SQL queries > to 1) detect if WSUS is in a bad state and 2) delete files from tbFile > table. This is all assuming that we have our WSUS databases in SQL. Well, > we are using a WID database in our environment… looking back, probably > would have done that differently, but whats done is done. How would I go > about running these queries against a WID database? It took me days to > finally get our WSUS environment working properly after upgrading to CM1606 > and upgrading our WSUS servers to 2012 R2. I’d hate to have to start all > over, but if I have to, I will. > > > > Thanks! > ------------------------------ > > *Confidentiality Notice:* This e-mail is intended only for the addressee > named above. It contains information that is privileged, confidential or > otherwise protected from use and disclosure. If you are not the intended > recipient, you are hereby notified that any review, disclosure, copying, or > dissemination of this transmission, or taking of any action in reliance on > its contents, or other use is strictly prohibited. If you have received > this transmission in error, please reply to the sender listed above > immediately and permanently delete this message from your inbox. Thank you > for your cooperation. > >
