Microsoft KB Archive/841057

= Support for changes to the databases that are used by Office server products and by Windows SharePoint Services =

Article ID: 841057

Article Last Modified on 11/6/2007

-

APPLIES TO


 * Microsoft Windows SharePoint Services 2.0
 * Microsoft Windows SharePoint Services 3.0
 * Microsoft Office SharePoint Portal Server 2003
 * Microsoft Office SharePoint Server 2007
 * Microsoft Office Forms Server 2007
 * Microsoft Office Groove Server 2007
 * Microsoft Content Management Server 2001 Enterprise Edition
 * Microsoft Content Management Server 2002

-



INTRODUCTION
The Microsoft Office server products that are listed in the &quot;Applies to&quot; 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.



MORE INFORMATION
The products that are listed in the &quot;Applies to&quot; section were tested by using the existing structure and were approved for release based on that structure. Microsoft cannot reliably predict the effect to the typical operation of these products when parties other than Microsoft support change the database or run stored procedures. Parties other than Microsoft support would include, but not be limited to, changes that are made by customers, by third-party vendors, or by consultants.

Examples of such database changes include, but are not limited to, the following:
 * Adding database triggers
 * Adding new indexes or changing existing indexes within tables
 * Adding, changing, or deleting any primary or foreign key relationships
 * Changing or deleting existing stored procedures
 * Adding new stored procedures
 * Running stored procedures manually or programmatically
 * Adding, changing, or deleting any data in any table of any of the databases for the products that are listed in the &quot;Applies to&quot; section
 * Adding, changing, or deleting any columns in any table of any of the databases for the products that are listed in the &quot;Applies to&quot; section
 * Any modification to the database schema
 * Adding tables to any of the databases for the products that are listed in the &quot;Applies to&quot; section

If a database modification is discovered during a support call, the customer must perform one of the following procedures:
 * Perform a database restoration from the last known good backup that did not include the database modifications
 * Roll back all the database modifications

If a good backup that does not include the database modifications does not exist, or if the customer is unable to roll back the database modifications, the customer must recover the data manually. The customer must do this before the customer opens a disaster recovery case to obtain help to migrate any recovered data to a new, unmodified database to return to a supportable database environment.

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. In rare circumstances and during a support incident, support may provide customers with a script that makes modifications to the databases that are used by the products that are listed in the &quot;Applies to&quot; section. In these cases, all modifications are reviewed by the development team to make sure that the operations being performed will not result in an unstable or unsupported database state.

Database changes that are made with the guidance of support during a support incident will not result in an unsupported database state. However, these support-guided actions do not negate the previous statements about customer modifications to these databases.

Additionally, customers must not make support-guided changes outside a support incident or provide such changes to other customers for use outside a support incident. In addition to the items previously mentioned, customers are strongly advised against direct access in a read-only manner to these databases. Accessing these databases programmatically or manually could cause unexpected locking within Microsoft SQL Server that can result in overall performance problems.

