Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

Windows Internal Database

This past Friday I received a call from our systems team stating that they were running low on Disk Space on a SQL Server server that their team used for Share Point.  He stated that there was an .LDF file that was really large, and could he just delete it.  Yeah, I said jokingly, but quickly retracted the statement because he was on his way.  I knew that the offending databases recovery model was set to Full and that they were not backing up the Transaction Log.

After getting a little information about the system, I determined that I could change the recover model to simple.  I logged into the machine to find the SQL Server instance name.  To my surprise I did not see a SQL Server running on the box.  I did however notice that a Windows Internal Database service was running as a Service on the Machine:

 

image

I immediately did a web search (Windows Internal Database), which resulted in several great listings.  I am not going to repeat what the articles stated, but I am going to provide a great link from MSSQLTips.com that helped me solve my problem.

Administering your Windows Internal Databases (Microsoft##SSEE) instance.

I installed SSMS Express, connected to the instance and changed the recovery model to Simple, problem solved.

Talk to you soon

Patrick LeBlanc, found TSQLScripts.com and SQLLunch

SQL Down South.

Comments

Posted by Tim Mitchell on 14 September 2009

Interesting... I haven't run into this before.  Thanks for the tip.

Posted by Steve Jones on 14 September 2009

Great catch, and this is good information to know.

Posted by george sibbald on 22 September 2009

good to know, especially the connection string,but could you not manage the SSEE instance remotely using SSMS installed on some other machine?

Posted by Patrick LeBlanc on 22 September 2009

That is a good question.  I have been searching for that answer.  If you prefer not installing SSMS express, you can also connect using SQLCMD or OSQL scripts.

Posted by fsilano on 22 September 2009

Great article. Thanks.

Posted by Tom Garth on 22 September 2009

Worthy tidbit, this. Thanks.

Posted by tplas on 22 September 2009

Yes, you can manage it remotely using SSMS from another machine --but ONLY if you've enabled the instance for remote connections (using SQL Surface Area Config tool). Specifically, remote connections with named-pipes, which also implies you're using Windows auth. And have Windows firewalls set properly.

Leave a Comment

Please register or log in to leave a comment.