Share via

SQL Server database is full - Event 3758 (SharePoint 2010 Products)

  • Article

 

Applies to: SharePoint Server 2010, SharePoint Foundation 2010

Alert Name:   SQL Server database is full

Event ID:   3758

Summary:   Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store most of the content for SharePoint Foundation Web site and configuration settings, and uses a service account to communicate with the database on behalf of a user request. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases. This error indicates that the database has reached the size of its maximum size setting.

Symptoms:   The following symptom might appear:

  • Users cannot add or update any content in SharePoint Foundation.

  • Administrators cannot update any SharePoint Foundation settings.

  • This event appears in the event log: Event ID: 3758 Description: Database full error on SQL Server instance <instance name> in database <database name>. Additional error information from SQL Server is included below. <SQL error message>

Cause:   The database has reached its maximum size.

Note

You must be a member of the Farm Administrators SharePoint group to perform the following tasks.

Resolution:   Increase the size of the SQL Server database

  • SharePoint Foundation cannot write to a database that has reached its maximum size. Increase the maximum size setting for the full database that is named in the event message.

    To increase the database size:

    1. In SQL Server Management Studio, in the Object Explorer navigation pane, expand the server node, and then expand the Databases node.

    2. Right-click the database you want, and then click Properties. The database name is provided in the event message.

    3. In the Database Properties dialog box, in the navigation pane, click Files.

    4. In the Database files section, in the Autogrowth column, click the ellipsis for the database file.

    5. In the Change Autogrowth dialog box, in the Maximum File Size section, if the Restricted File Growth option is selected, increase the maximum file size in the box to the right. You can also configure the database to grow without restrictions by selecting the Unrestricted File Growth option.

    6. Click OK to save changes.

    To verify that database issues are resolved:

    1. In the SharePoint Management Shell, run the Windows PowerShell command Get-SPSite | Format-Table -Property ID,WebApplication,ContentDatabase to obtain a list of the sites for each Web application to list all sites in the various databases, and locate one site in each database.

    2. Browse to the site.

    3. Try to add content to the site. For example, add a list item or a document. SharePoint Foundation uses different errors under different editing circumstances, so if adding content to the site fails, check the event log for an error message such as those in the following table.

      Log Name:

      Application

      Source:

      Microsoft-Windows SharePoint-Windows SharePoint Services 4

      Date:

      4/2/2009 6:34:13 AM

      Event ID:

      3758

      Task Category:

      Database

      Level:

      Critical

      Keywords:

      User:

      Domain\Myuser

      Computer:

      MyServer

      Description:

      Database full error on SQL Server instance 'CO137' in database 'wss_2'. Additional error information from SQL Server is included below. Could not allocate space for object 'dbo.AllDocs'.'AllDocs_Url' in database 'wss_2' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.