Windows Internal Database & SBS 2008

You probably wondered why some things are slow, especially if it is SBS server. On a server you have installed Exchange, Sharepoint, IIS, Remote Admin site, AD and lot of small applications. Among other things you have installed the database for WSUS, Sharepoint Services and SBS monitoring application. Databases for Sharepoint and WSUS are on the Windows Internal Database database engine . As you know, or do not know, this database need also from time to time some administration. The first thing is to get to databases itself. These databases are accessible only via named pipes path so you enter the following in SQL Management Studio \\.\pipe\mssql$microsoft##ssee\sql\query in order to connect to the database engine. Here is an example from the SBS 2008 server. Refer to the service name of your database instance (Microsoft # # SSEE) and enter it accordingly. Usually the same name everywhere. We have also an SBS server feature/problem. We will not be able to access the database. The admin of the database is domain Administrator account. It is disabled by default on SBS.  Turn it on and put a password. What to say, “Now we are in business.” Start SQL Management Studio under that account, and we are there. What to look for now. I found that the log of the Sharepoint configuration database size is 2GB (If you do not know how to get this going at Report > Standard Reports> Disk usage)

image

It is not that big but trust me when you have a lot of this size databases on an SBS machine then each byte matter. How to reduce this. I will not go into details about why and how, do backup first in this way. First full database backup, then backup the transaction logs. Those who know something about databases explanation is not needed, and those who doesn’t know just do so. (Very important do not skip backup logs). When you do this right click on the database / log that you want to reduce, and go to Tasks> Shrink> Files. You will get dialog box with database file selected, which you probably can not shrink because of lack of free space in the database. Watch AVAILABLE free space column. In my case, 8% with respect to the database size of 7 MB is irrelevant. However when you selected in File type Log instead of Data we have something much better. AVAILABLE free space is 98% or almost 2GB.

image

To shrink the log file, select this option as shown on picture above and enter the desired value in file size. Once again, make sure that nothing has happened. I myself was surprised the first time. But there is no surrender. Do once more backup of transaction log. Well now, do again shrinking of log file procedure and you will get what you need (see picture). Do this for the rest of the database, if they need it, and defragment the disk afterwards. I think the system will have a much faster response and hard drive led will work less often than before.

image