So a little Googling and up popped an Experts Exchange thread that had the information embedded – With the Express Management Studio GUI and a couple of clicks it was all sorted. My _log.ldf file was well over 30GB! Also, the drive was less that 1% from full. What had occurred is that this separate and experimental lab server doesn’t have a regular backup routine consequently, SQL’s log grows and grows until a backup is made. ***now months later I found this critically important to a SharePoint installation that was using this database instance. options -> network protocol: Named Pipes.Server name: ‘\\.\pipe\mssql$microsoft#ssee\sql\query’ (no quotations).Connect the SQL Instance using named pipe.open SQL Server Management Studio Express **As Administrator** (if in a newer OS where that is an option).Download and install the SQL Server Management Studio Express (if no SQL management tool is available).You optionally could also use SQLCMD or OSQL scripts. In SQL Server Management Studio UI you must use a named pipe identity in order to connect to this instance. If you ever need to get at the databases contained in the instance you will find that this isn’t conventional. The instance is noted by a name of ‘MICROSOFT#SSEE’. These include WSUS 3.0 and WSS 3.0 (SharePoint Services). Several Microsoft applications require databases that utilize the Windows Internal Database aka SQL Server 2005 Embedded Edition.
0 kommentar(er)
