Microsoft products such as Windows Server Update Services (WSUS) 3.0 and Windows Sharepoint Services (WSS) 3.0 come with SQL Server 2005 Embedded Edition, now known as the Windows Internal Database. For system administrators who are not full-fledged DBAs, managing these databases can be a challenge. In this article, we will explore how to effectively manage the Windows Internal Database.
Understanding the Windows Internal Database
The Windows Internal Database is an embedded data service that is specifically designed to be used by a limited number of Windows Services. It is not intended for use with non-Microsoft products. When you install WSUS 3.0 or WSS 3.0, the databases are created on the C:\ partition by default, which can lead to administration issues such as insufficient disk space.
Using SQL Server Management Studio Express
The easiest way to manage the Windows Internal Database is by using SQL Server Management Studio Express. You can install a copy of SQL Server Management Studio Express on the server running WSUS 3.0 or WSS 3.0. To connect to the Windows Internal Database, you need to register the instance using Named Pipes. The server name for registration is \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query.
Once you have registered the instance in SQL Server Management Studio Express, you can perform various administrative tasks such as shrinking the database files or moving them to a different disk partition dedicated for them to avoid insufficient disk space issues.
Using SQL Server 2005 Command Line Query Utility
If you prefer to use scripts to manage the Windows Internal Database, you can download and install the SQL Server 2005 Command Line Query Utility – sqlcmd. This tool is installed by default in the directory C:\Program Files\Microsoft SQL Server\90\Tools\binn.
To connect to the database instance using sqlcmd, you need to run the sqlcmd.exe utility, passing the instance name and your credentials. The command would be:
sqlcmd -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -EOnce connected to the database instance, you can run your administrative T-SQL scripts.
Considerations
While it is possible to administer the Windows Internal Database, it is important to note that making modifications to the database schema or properties is not recommended. Doing so can break the supportability of WSUS 3.0 and WSS 3.0. Additionally, any changes made to these databases can be overwritten by the products’ service packs or cumulative updates.
In conclusion, managing the Windows Internal Database in SQL Server requires the use of tools such as SQL Server Management Studio Express or the SQL Server 2005 Command Line Query Utility. It is important to follow best practices and avoid making modifications that could impact the supportability of the associated Microsoft products.