Since SharePoint 2013 Public Update March 2013 there is a problem in Central Admin -> Manage Databases Upgrade Status where the Business Connectivity Database shows, that it is in compatibility Range and Upgrade is recommended.
Normally you can use PSCONFIG.EXE -cmd upgrade -inplace b2b (found in the c:\program files\common files\microsoft shared\webserver extensions\15\bin) to upgrade any database in compatibility mode. Also the Upgrade-SPContentDababase Command would be handy, if it was a Content Database. As in our scenario nothing of it works, I did some investigation and found, that it could be done with the Provision() method of the SharePoint API. There it states:
Was immer mal wieder gefragt wird ist, was man denn genau für SharePoint Datenbanken für Maintenance Tasks machen muss und welche Operationen auf SharePoint Datenbanken erlaubt sind und welche nicht.
Ich habe im Folgenden mal alles, was eigentlich auch im Technet bekannt aber verstreut oder unübersichtlich ist, zusammengefasst. Zusätzlich gibt es einen SQL Best Practice Skript, der die benötigten Aktionen automaisch erstellt. Viel Spass beim lesen
So long, Samuel
|Database||Recommended Recovery Model||Backup Method||Size||Characteristics||Notes|
|Config||Simple||SP BackkupSQL Backup||Small||Read intensisve||
|Central Administration Content||Full||SP BackupSQL Backup||Small||Varies||
|Content Databases||Full||SP BackupSQL Backup||Small to Big||Varies by Usage||
|App Management||Full||SP BackupSQL Backup||Small||Write heavy||
|Business data Connectivity||Full||SP BackupSQL Backup||Small||Read heavy||
|Search – Admin||Simple||SP BackupSQL Backup||Medium||Read Write||
|Search – Analytics||Simple||SP BackupSQL Backup||Medium to Large||Write heavy||
|Search – Crawl||Simple||SP BackupSQL Backup||Medium||Read heavy||
|Search – Link||Simple||SP BackupSQL Backup||Medium to Large||Write heavy||
|Secure Store||Full||SP BackupSQL Backup||Small||Equal Read Write||
|Usage||Simple||SQL Backup||XLarge||Write heavy||
|Subscription Settings||Full||SP BackupSQL Backup||Small||Read heavy||
|User Profile – Profile||Simple||SP BackkupSQL Backup||Medium to Large||Read heavy||
|User Profile – Sync||Simple||SP BackupSQL Backup||Medium to Large||Equal Read Write||
|User Profile – Social||Simple||SP BackupSQL Backup||Small to XLarge||Read heavy||
|Word Automation||Full||SP BackupSQL Backup||Small||Read heavy||
|Managed Metadata||Full||SP BackupSQL Backup||Medium||Read heavy||
|Machine Translation||Full||SP BackupSQL Backup||Small||Read heavy||
|Project Server||Full||SP BackupSQL Backup||Small to Medium||Read heavy||
|PowerPivot||Full||SP BackupSQL Backup||Small||Read heavy||
|Performance Point||Full||SP BackupSQL Backup||Small||Read heavy||
|State Service||Full||SP BackupSQL Backup||Medium to Large||Read heavy||
|Report Server – Catalog||Full||SQL Backup||Small||Read heavy||
|Report Server – Temp||Full||SQL Backup||Small to XLarge||Read heavy||
|Report server – Alerting||Full||SQL Backup||Small to XLarge||Equal Read Write heavy||
These advices were published for SharePoint 2010 but mainly still apply for SharePoint 2013. Only the Timer Jobs might have changed that do automatic Index Maintenance. For all Databases that are used for SharePoint 2013 Content do regularly Database Maintenance.
|DBCC CHECKDB||All SharePoint DBs||Weekly of before each Full Backup||
|Index Rebuilding||All SharePoint DBs||Depends on:- If Database has a Timer Job
- Fragmentation Level
|AutoShrink||All SharePoint DBs||Never||
|Maintenance Cleanup||All SharePoint DBs||Weekly or with scheduled maintenance plans|
The Microsoft Office server products 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.
SharePoint Products 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:
- 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
- Adding new stored procedures
- Adding, changing, or deleting any data in any table of any of the databases for SharePoint
- Adding, changing, or deleting any columns in any table of any of the databases for SharePoint
- Making any modification to the database schema
- Adding tables to any of the databases for SharePoint
- 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.)
- Enabling SQL Server change data capture (CDC)
- Enabling SQL Server transactional replication
- Enabling SQL Server merge replication
If an unsupported database modification is discovered during a support call, the customer must perform one of the following procedures at a minimum:
- 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 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.
Exceptions to the prohibition against database modifications are made for specific usage scenarios:
- Operations that are initiated from the SharePoint administrative user interface
- SharePoint specific tools and utilities that are provided directly by Microsoft (for example, Ststadm.exe)
- Changes that are made programmatically through the SharePoint Object Model and that are in compliance with the SharePoint SDK documentation
- Activities that are in compliance with the SharePoint Protocols documentation
Additionally, in rare circumstances during a support incident, Microsoft SharePoint Support agents may give customers scripts that modify the databases that are used by SharePoint. In these cases, all modifications are reviewed by the SharePoint Development Team to ensure that the operations being performed will not result in an unstable or unsupported database state. Database changes that are made with the guidance of a Microsoft SharePoint Support agent during the course of a support incident will not result in an unsupported database state. Customers may not reapply the scripts or changes provided by Microsoft SharePoint Support outside of a support incident.
Reading 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.
The SQL Server Maintenance Solution comprises scripts for running backups, integrity checks, and index and statistics maintenance on all editions of Microsoft SQL Server 2005, SQL Server 2008, SQL Server 2008 R2, SQL Server 2012, and SQL Server 2014. The solution is based on stored procedures, the sqlcmd utility, and SQL Server Agent jobs. I designed the solution for the most mission-critical environments, and it is used in many organizations around the world. Numerous SQL Server community experts recommend the SQL Server Maintenance Solution, which has been a Gold winner in the 2013, 2012, 2011, and 2010 SQL Server Magazine Awards. The SQL Server Maintenance Solution is free.
Es freut mich mitzuteilen, dass Experts Inside bei der Office 365 Readyness Competition von Microsoft Schweiz den ersten Platz ergattern konnte.
Hier ist das Video welches wir für die Finaleinreichung verwendet haben:
Und hier die Präsentation. Gerne halte ich diese auch bei Ihnen vor dem Management, der Technik oder den Endbenutzern.
So Long, Samuel
Nach dem Release von SharePoint 2013 SP1 Ende Februar 2014 gab es Probleme mit dem Servicepack. Es waren zwar keine Funktionalitäten betroffen, jedoch konnten keine weiteren Updates installiert werden, nachdem SP1 installiert war.
Dies konnte nun behoben werden, ab sofort ist SP1 für SharePoint 2013 wieder dowloadbar: http://www.microsoft.com/en-us/download/details.aspx?id=42544
So long, Samuel
SharePoint 2013 Service Pack 1
By Joerg Sinemus
For all our Office Server 2013 products we can offer now the first service pack SP1.
In case you have a SharePoint Foundation 2013 Server, you need only the SP1 for Foundation and of course language packs for Foundation SP1.
For our full SharePoint 2013 Server you only need the SharePoint Server SP1 package. There is no need to install Foundation SP1 because it is included in the Full Server SP1. Same is valid for the additional SP1 language packs you may need when having at least one additional LP installed.
For Project Server 2013 you also need only the Project SP1 plus SP1-LP’s when you have additional LP’s installed.
Our KB articles for your reference:
KB 2817442 – SharePoint Foundation 2013 SP1
KB 2817429 – SharePoint Server 2013 SP1
KB 2817434 – Project Server 2013 SP1
KB 2817431 – Office Web Apps Server 2013 SP1
Service Pack 1 also includes a rollup of all Cumulative Updates through December 2013, and all Public Updates through January 2014.
When our next April 2014 CU will be available it can be installed on top of SP1.
Download links for SP1:
SharePoint Foundation 2013 Service Pack 1
SharePoint Foundation 2013 Language Pack Service Pack 1
SharePoint Server 2013 Service Pack 1
SharePoint Server 2013 Language Pack Service Pack 1
Project Server 2013 Service Pack 1
Office Web Apps Server 2013 Service Pack 1
Good references to know:
Issues Fixed by Service Pack 1 (SP1) in Office and SharePoint 2013
Software updates overview for SharePoint 2013 great articles to plan and test all the steps you need to know until your production is on the latest bits.
Office Sustained Engineering Blog more about SP1
View this post online.
Dieses Video richtet sich an Entscheidungsträger, Projektleiter aber auch Technische Verantworltiche, die ihren Kunden gerne erklären würden, warum SharePoint eine gute Wahl für ihr Unternehmen ist. Es entlarvt die gängigen Fallstricke in der Zusammenarbeit und zeigt die gröbsten Vorteile von SharePoint verständlich auf.
Viel Spass beim zuschauen und teilen
So Long, Samuel
Hier mal noch das neuste Werk von mir, wo ich zeige, wie man SharePoint 2013 mit SQL, WebApps und Workflow Manager installiert. Inklusive aller Powershell Scripts für das Setup. Alles nach bisher bekannten Best Practices, auch für die SharePoint Topologie etc.
So long, Samuel