Article ID: 841057 - View products that this article applies to.
The Microsoft Office server products that are listed in the "Applies to" section store data in Microsoft SQL Server databases. These products use various stored procedures for regular processing. Therefore, the Microsoft SQL Server databases are important to the successful operation of these products.
The products that are listed in the "Applies to" section were tested by using a database structure as designed by the SharePoint Development Team and were approved for release based on that structure. Microsoft cannot reliably predict the effect to the operation of these products when parties other than the Microsoft SharePoint Development Team or Microsoft SharePoint Support agents make changes to the database schema, modify its data, or execute ad hoc queries against the SharePoint databases. Exceptions are described in the "Supported Database Modifications" section.
Examples of unsupported database changes include, but are not limited to, the following:
If an unsupported database modification is discovered during a support call, the customer must perform one of the following procedures at a minimum:
If a previous version of the database that does not include the unsupported modifications is unavailable, or if the customer cannot roll back the database modifications, the customer must recover the data manually. The database must be restored to an unmodified state before Microsoft SharePoint Support can provide any data migration assistance.
If it is determined that a database change is necessary, a support case should be opened to determine whether a product defect exists and should be addressed.
Supported database modificationsExceptions to the prohibition against database modifications are made for specific usage scenarios:
Read operations addendumReading from the SharePoint databases programmatically, or manually, can cause unexpected locking within Microsoft SQL Server which can adversely affect performance. Any read operations against the SharePoint databases that originate from queries, scripts, .dll files (and so on) that are not provided by the Microsoft SharePoint Development Team or by Microsoft SharePoint Support will be considered unsupported if they are identified as a barrier to the resolution of a Microsoft support engagement.
If unsupported read operations are identified as a barrier to the resolution of support engagement, the database will be considered to be in an unsupported state. To return the database to a supported state, all unsupported read activities must stop.
Commercial Independent Software Vendor (3rd party) addendumMicrosoft strictly prohibits all 3rd party modifications to SharePoint databases. As such, installing or using any 3rd party tool which modified data stored in SharePoint databases will result in that entire SharePoint farm becoming unsupported.
For more information about support for changes to the databases that are used by SharePoint and related Office Server products, review the following article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/932744/ )Information about the Maintenance Plan Wizard in SQL Server 2005 and about tasks that administrators can perform against SharePoint databases
(http://support.microsoft.com/kb/930887/ )You experience issues with portal alerts in SharePoint Portal Server 2003 or with search performance in SharePoint Server 2007 after you create SQL Server 2005 maintenance plans
Article ID: 841057 - Last Review: July 9, 2014 - Revision: 23.0