Business Connectivity Database is in compatibility range and upgrade is recommended -en-

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:


SQL Server Maintenance für SharePoint

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


1       Database Maintenance Plan for SharePoint. 2

1.1        Databases in SharePoint 2013. 2

1.2        Database Maintenance. 4

1.3        Supported and Unsupported Chagnes on SharePoint DBs. 5

1.3.1         Unsupported Database Changes. 5

1.3.2         Supported database modifications. 6

1.3.3         Read operations addendum.. 7

2       SQL Maintenance Script7





1         Database Maintenance Plan for SharePoint

1.1         Databases in SharePoint 2013


Database Recommended Recovery Model Backup Method Size Characteristics Notes
Config Simple SP BackkupSQL Backup Small Read intensisve
  • Must be Co-Located with CA DB
  • Recovery Model must be full for Mirroring
  • Scale up, only one DB per Farm
Central Administration Content Full SP BackupSQL Backup Small Varies
  • Must be Co-Located with Config DB
  • Can grow over the period of 365 days if Power Pivot is used
  • Scale up, only one DB per Farm
Content Databases Full SP BackupSQL Backup Small to Big Varies by Usage
  • Limit Size to 200GB per Content DB
  • Scale out, Scale up (a Site Collection can sit in only 1 DB)
App Management Full SP BackupSQL Backup Small Write heavy
  • Only write heavy during App installation
  • Scale up, Scale out only on Office 365
Business data Connectivity Full SP BackupSQL Backup Small Read heavy
  • Scale up, only one DB per Farm
Search – Admin Simple SP BackupSQL Backup Medium Read Write
  • Scale up, Scale out only by creating additional Service Applications
Search – Analytics Simple SP BackupSQL Backup Medium to Large Write heavy
  • Nightly Analytics update
  • Scale out by Split Operation when DB becomes > 200GB
Search – Crawl Simple SP BackupSQL Backup Medium Read heavy
  • Scale out by creating new DBs for every 20mio Items crawled
Search – Link Simple SP BackupSQL Backup Medium to Large Write heavy
  • Affected by Content processing
  • Scale out by creating new DBs for 60mio Items crawled and for expected 100mio querys per year
Secure Store Full SP BackupSQL Backup Small Equal Read Write
  • Scale up, Scale out by creating new Service Applications
Usage Simple SQL Backup XLarge Write heavy
  • Scale up, only one DB per Farm
Subscription Settings Full SP BackupSQL Backup Small Read heavy
  • Scale up, Scale out by creating new Service Applications
User Profile – Profile Simple SP BackkupSQL Backup Medium to Large Read heavy
  • Scale up, Scale out by creating new Service Applications
User Profile – Sync Simple SP BackupSQL Backup Medium to Large Equal Read Write
  • Scale up, Scale out by creating new Service Applications
User Profile – Social Simple SP BackupSQL Backup Small to XLarge Read heavy
  • Scale up, Scale out by creating new Service Applications
Word Automation Full SP BackupSQL Backup Small Read heavy
  • Scale up, Scale out by creating new Service Applications
  • Traffic is Affected by Word Conversions only
Managed Metadata Full SP BackupSQL Backup Medium Read heavy
  • Scale up, Scale out by creating new Service Applications
Machine Translation Full SP BackupSQL Backup Small Read heavy
  • Scale up, Scale out by creating new Service Applications
Project Server Full SP BackupSQL Backup Small to Medium Read heavy
  • Scale up
  • One Database per Project WebApp
PowerPivot Full SP BackupSQL Backup Small Read heavy
  • Scale up
Performance Point Full SP BackupSQL Backup Small Read heavy
  • Scale up, Scale out by creating new Service Applications
State Service Full SP BackupSQL Backup Medium to Large Read heavy
  • Scale out by creating additional Databases
Master Simple SQL Backup Small Varies
Model Full SQL Backup Small Varies
Msdb Simple SQL Backup Small Varies
Tempdb Simple SQL Backup Medium Varies
  • Locate on fast Disks and split Database to several Datafiles
Report Server – Catalog Full SQL Backup Small Read heavy
  • Scale Up
Report Server – Temp Full SQL Backup Small to XLarge Read heavy
  • Scale Up
Report server – Alerting Full SQL Backup Small to XLarge Equal Read Write heavy
  • Scale Up
  • Must be on same Server as the Repprt Server – Catalog

1.2         Database Maintenance


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.

Action Databases Frequency Notes
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


Fragmentation methods


Fragmentation level Defragmenta-tion method
Up to 10% Reorganize (online)
10-75% Rebuild (online)
75% Rebuild (offline)
  • Online Index Rebuild only for SQL Enterprise
  • Fallback from Online to Offline Index Rebuild might occur on special occasions (e.g. for LOB Columns)
  • Many of the SP Indexes are rebuilt Offline because of LOB Content (like documents, Pictures etc.)
  • Offline and Online Index Rebuild result in Locks or inaccessibility of Indexes and should therefore be done in low activity times
  • Use “sys.dm_db_index_physical_stats” to measure Fragmentation. Values from 0 to 10 in Column “avg_fragmentation_in_percent” are acceptable
  • SharePoint Timer Jobs (Health Rules) are doing a part of Index defragmentation and Stats updates
  • Timer Jobs look for its associated databases and performs proc_DefragmentIndices stored procedure on int. Indexes with Fragmentation > 30% are considered for reindex
  • Not all Databases have Timer Jobs and should be monitored manually
  • Using DROP INDEX or CREATE INDEX Operations are NOT supported on SharePoint Databases
AutoShrink All SharePoint DBs Never
  • Better Solution is to create a new database, move the Site Collections and delete the old database
  • Only if there is definitely a very high amount of unused space and you do not plan to reuse it and only for Content Databases
  • EMPTYFILE Option is not supported
  • TRUNCATEONLY Option is not supported
Maintenance Cleanup All SharePoint DBs Weekly or with scheduled maintenance plans


1.3         Supported and Unsupported Chagnes on SharePoint DBs

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.

1.3.1        Unsupported Database Changes

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.

1.3.2        Supported database modifications

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.

1.3.3        Read operations addendum

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.

2         SQL Maintenance Script


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.


Das Gewinnervideo der Office 365 Readyness Competition bei Microsoft Schweiz

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

Probleme mit SharePoint 2013 SP1 behoben

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:

So long, Samuel

SharePoint 2013 Service Pack 1

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.

Die Collaboration User Story – Warum braucht es ein Collaboration Tool?

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

Best Practices Setup von SharePoint 2013, mit Web Apps 2013 und Workflow Manager 1.0

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

Weltkonzern Intel droht Schweizer Kleinfirma

Der amerikanische Chip-Hersteller versucht über seine Anwälte ein junges St. Galler Unternehmen zu einem anderen Namen zu zwingen.

VonChristian Bütikofer


IT-Riese Intel droht Schweizer Firma mit Klage

Intel: Der Chip-Hersteller hat gar keine Freude am Beratungsunternehmen «Experts Inside» aus St. Gallen. (Bild: Bloomberg)

Intel hat ein Problem mit dem Schweizer Beratungsunternehmen «Experts Inside». Der amerikanische Konzern setzte die deutsche Anwaltskanzlei Lichtenstein, Körner & Partner auf die Kleinfirma aus Zuzwil SG an, weil die Schweizer angeblich die Rechte von Intels Marke «Intel Inside» verletzen. Das berichtet das Informatik-Magazin «Computerworld».

Die Anwälte verlangen in einem 35 Seiten langen Dokument von den Schweizern einen Nutzungsverzicht und das Löschen der in Deutschland eingetragenen Marke «Experts Inside». Das Anwaltsschreiben liegt vor. Die Anwälte sind gnädig: «Unsere Mandantin würde es vorziehen, die Angelegenheit auf diese Weise einvernehmlich und ohne weitere Folgekosten […] zu regeln», ist darin zu lesen. In der vorausgefüllten Unterlassungserklärung nennen die Anwälte eine Vertragsstrafe von 7500 Euro pro allfälliger Nutzung des Namens Experts Inside – auch als Second-Level-Domain.

Intel schweigt

Geschäftsführer Samuel Zürcher von Experts Inside sagte Computerworld, dass das Unternehmen zusammen mit seinen Anwälten die Forderungen Intels prüfe. Gemeinsam mit dem deutschen Niederlassungsleiter Christian Glessner habe es Experts Inside geschafft, die Firma unter dem aktuellen Namen bekannt zu machen und zu etablieren.

Intels Mediensprecher Nicola Procaccio wollte die Aktion der Anwälte nicht kommentieren. Im Schreiben der Deutschen wurde auch kein Kontakt zu Intel angegeben. Die Anwaltskanzlei Lichtenstein, Körner & Partner versucht die Schweizer mit 146 Fällen zu beeindrucken, die Intel angeblich bei ähnlichen Streitigkeiten gewonnen habe. Da wird mit grossen Namen geworben, etwa Deutsche Telekom, Daimler, Siemens oder Sony.

Schwammige juristische Kraftmeierei

Doch die juristische Kraftmeierei steht auf tönernen Füssen: 2010 hat das europäische Harmonisierungsamt für den Binnenmarkt entschieden, dass «inside» im Sinne von «innerhalb» international verständlich ist und es sich deshalb nicht schützen lässt. Damals ging Intel gegen die Bezeichnung «Autolearning Inside» vor – und zog den Kürzeren.

Intel Inside: Swiss allegedly infringe trademark

This is a Computerworld Post that was translated into English.
Link to original Post:

Intel accuses the IT-consulting company Experts Inside for infringing the registered trademark «Intel inside» . The St. Galler are not the first «Insiders» with this problem.

David versus Goliath: The Swiss IT-consulting company Experts Inside is facing a trademark litigation with Intel. The semiconductor-giant considers the rights relating to his trademark «Intel inside» to have been infringed by the use of the name component «Inside». In a letter to Experts Inside, which was presented to Computerworld, the Stuttgart-based law firm Lichtenstein, Körner & Partner certifies a «conflict with the famous trademark» of its client Intel.

The lawyers demand from the Swiss, the immediate non-utilization and deletion of the trademark «Experts Inside», which is registered in Germany. «Our client would thus prefer to regulate the matter mutually and without additional follow-up costs […]», according to the letter. In a prefilled cease and desist agreement, the lawyers shall call a contractual penalty of Euro 7500 for each possible use of the name Experts Inside – also as second-level-domain.

As Samuel Zürcher, the Managing Director of Experts Inside, said to Computerworld, the company is currently checking the claims together with its lawyers. Zürcher, together with the German Branch Manager Christian Glessner, has managed to publicize and establish the company under the current name. «We have worked too hard and applied too much for letting us simply ruin by such a claim», said Zürcher. Experts Inside had approached the Law firm and had signaled willingness to talk. The opposition however adhere to the claim and also deny a direct contact with Intel.

Nicola Procaccio, Intel’s Communication and Media Relations Manager Southern Europe & Switzerland, clarified at the request of Computerworld: «We do not comment on ongoing proceedings.»

Experts Inside are not the first company, which came into conflict with the semiconductor giants due to the name affix. In the letter, the Stuttgart-based lawyers shall mention additional cases, in which Intel has defended the trademark in the past «extremely successful against the acquisition of ‚inside’». A list with 146 name conflicts, which the group wants to have decided in its favor, is attached to the document. Name creations with the component «Inside» are listed by companies like AEG, DaimlerChrysler, Deutsche Telekom, Opel, Siemens and Sony.

It is however not clear from the report of Stuttgarters, whether the trademark deletions are fought in court or are concluded by any other way. In any case, the companies might have also «voluntarily» cancelled their trademarks considering the impending cost risk.

The law firm Dury, which is appointed by Experts Inside, is hopeful on request by Computerworld to be able to bring the case to a positive end for its clients. They quote a decision of the European Office for Harmonization in the internal market (OHIM) from the year 2010. The OHIM had meanwhile decided that «inside» would be internationally understandable in terms of «within» and would thus pertain to distinctive element (Ref: R0955/06-2). A reference to this case law is missing in the letter of the Intel-lawyers.

Mark Schröder, Editor Computerworld