Connecting to a Windows Internal Database (WID, codename WYukon) with SQL SServer Management Studio Express is possible. However, not over the network.
WSUS 3 by default stores its metadata in the "Windows Internal Database". According to wikipedia, this is an embedded version of SQL Express, which ships with Win2k8, Sharepoint Services and WSUS.
So, how move this datastore around?
As with a regular SQL Server datastore, you can detach and move the database.
Download and install required tools
I got the tools from the microsoft website. I downloaded sqlncli.msi and SQLServer2005_SQLCMD.msi
Stop services
The following services must be stopped to be able to detach the database: IIS Admin Service and Update Services (Not Windows Update Service!). To do this, run: net stop "update services" net stop w3svc
2. Now move the SUSDB.mdf and SUSDB.ldf to their new location. In the example below, we use E:\WSUSDB\. Use explorer to move the files to the path you'd like.
3. Then we reattach the database: "c:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD.EXE" -E -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -Q "sp_attach_db @dbname=N'SUSDB',@filename1=N'E:\WSUSDB\SUSDB.mdf', @filename2=N'E:\WSUSDB\SUSDB_log.ldf'"
Restart services
Restart the services we stopped before. To do this, run: net start "update services" net start w3svc
Related info
If you want to move the WSUS data itself as well, please see this page
I recently installed a new Microsoft WSUS server. Most of it went just fine. Except for a few updates that weren't needed according to windowsupdate.com, but were required according to WSUS.
Especially KB974417 was pretty annoying. I tried installing it a dozen times, but after each reboot, WAU came back telling the update was ready to install. I checked out the eventvwr, and got the following useless message: Event Type: Error Event Source: HotFixInstaller Event Category: None Event ID: 5000 Date: 3/16/2010 Time: 3:06:25 PM User: N/A Computer: PC1 Description: EventType visualstudio8setup, P1 microsoft .net framework 2.0-kb974417, P2 1033, P3 1642, P4 msi, P5 f, P6 9.0.40302.0, P7 install, P8 x86, P9 w2k3r2, P10 0.
Installing it manually
I downloaded the file from the Microsoft website, to find that the update itself thought itwasn't needed as well: None of the products that are addressed by this software update are installed on this computer. Click Cancel to exit setup.
I'm using WordPress as a framework for a website that reaches over 30.000 readers daily over several media. Some over the web, but most users receive posts by mail, sms or twitter using custom-made plugins. Since I can't have a broken mail sent to thousands of users, I rather don't upgrade WordPress, except when security issues have been found. Every single WordPress upgrade I've done has broken something, like when plugin hooks are renamed, and renamed back later....
Timezone support broken
After my latest upgrade, the sending queue got seriously screwed up. SMS messages that should have been sent around 8am, got send around midnight. Why? Because WordPress timezone support screws up the time!
WordPress gave me my WTF moment while testing with date(). I've been testing what was wrong, and came across a situation where a simple reload caused the timezone to shift 2 hours. This simple line of code echoed 1:30:00 at 1:30:00 while echoing 3:30:01 at 1:30:01: <?php echo date("H:i:s"); ?>
This isn't such a problem for simple posts on a weblog, but for sending queued mail and sms messages this is fatal.
My solution
Screw WordPress. It'll get fixed in some future version of WordPress. For now I'll get a date I can actually trust from mysql: $wpdb->getvar('select DATE_FORMAT(current_timestamp,"%H:%i:%s");');
I also replaced several other instances of date(), like: "select * from wp_receipients where time_to_sent<".date("Hi")."'"; to 'select * from wp_receipients where time_to_sent<DATE_FORMAT(current_timestamp,"%H%i")';