| Article Summary: |
Unsupported Operations in SharePoint 2010 SQL Databases |
One example of an operation that leaves SQL in an unsupported state are reading from a SharePoint database is prohibited. Here are a few other operations that Microsoft specifically list as leaving a database in an unsupported state:
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
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.)
However, the following routine maintenance is recommended by Microsoft
· Checking database integrity (ensures that your data and indexes are not corrupted).
· Defragmenting indexes by either reorganizing them or rebuilding them (applies mainly to indexes; fragmentation can be reduced by setting a large database start size).
· Setting the fill factor for a server (allows index performance to be fine tuned).
· Shrinking databases to recover unused disk space (white space caused by deleting documents, libraries, lists etc.).
Note that it is not recommend configuring auto-shrink operations, and advise only to shrink content databases due to the fact that other types of databases (e.g. SSP) do not typically undergo a large number of deletions.