[Support Policy] Support for changes to the databases that are used by SharePoint

https://support.microsoft.com/kb/841057

Examples of unsupported 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
• Calling existing stored procedures directly, except as described in the SharePoint Protocols documentation (https://msdn.microsoft.com/en-us/library/cc339475.aspx)
• Adding new stored procedures
• Adding, changing, or deleting any data in any table of any of the databases for the products that are listed in the "Applies to" section
• Adding, changing, or deleting any columns in any table of any of the databases for the products that are listed in the "Applies to" section
• Making any modification to the database schema
• Adding tables to any of the databases for the products that are listed in the "Applies to" section
• Changing the database collation
• Running DBCC_CHECKDB WITH REPAIR_ALLOW_DATA_LOSS (However, running DBCC_CHECKDB WITH REPAIR_FAST and REPAIR_REBUILD is supported, as these commands only update the indexes of the associated database.)

Comments

• Anonymous
  November 10, 2011
  What about the logging database? This is said to be customizable to some degree? How does that fit in with these guidelines?
• Anonymous
  December 07, 2011
  Hi Bill, however....for DB change, no matter what kind of change it is, the official answer is always NO