Administering your Windows Internal Database MICROSOFT##SSEE instance

Submitted by Tom L'Ecluse on Sat, 29/12/2012 - 17:45

Had a Windows Small Business server 2012 which was short of memory. I saw that the internal database had more than 2Gb of ram (Of the 8Gb total) and the internal database was used for SharePoint (Which they don't use) and the WSUS server. So basically the these program blocked the real important services! The problem was. How can I change the database settings?

1. Open the “SQL Server Management Studio Express”

Just launch the SQL Server Management Studio Express”

Enter the following settings in the connect to server dialog box.

Server name: \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
Authentication: Windows Authentication.

Windows Internal Database

2. Manage your database.

Now that you have access to the database you can manage the database.

  • You can shrink the database.
  • You can move the database.


While there are possible reasons to administer the Windows Internal Database, it is not recommended to do anything beyond performing backups, moving or shrinking the database files.

Modifying database schema or database properties would break supportability of these products. Plus, any changes made to these databases can be overwritten by the products' service packs or cumulative updates.

Post new comment

The content of this field is kept private and will not be shown publicly.
To prevent automated spam submissions leave this field empty.
By submitting this form, you accept the Mollom privacy policy.