SharePoint Doctors Performance Tuning Case Study

September 25, 2014 by Joel Jeffery

There’s a new post from Dr. Kinley’s Facebook, over at SharePoint Doctors: The Case of the SharePoint Tuning Emergency.

Read the story of how the SharePoint Doctors helped restore the performance of a SharePoint farm that had suddenly ground to a halt.

#spthingaday

View on Instagram

Link to display lightbox

Instagram post 17912856886012897

#spthingaday 003 - Information Architecture. Folders are evil. Use metadata. #SharePoint, #Office365..
On a fileshare, all you have is path and filename. That's the only axis by which you can classify your stuff. So you nest folders, within folders, within folders. Then you pack the filename with extra bits of information - like the initials of the last editor, or the version number.
You don't need to do this in SharePoint. Use metadata.
Add columns to your libraries. Text columns, number columns, choice columns, managed metadata columns. Each file can have several of these values simultaneously. But a file can only live in one folder at a time.
Use metadata.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

14 0

View on Instagram

Link to display lightbox

Instagram post 17903287741076397

#spthingaday 010 - SharePoint Online. Modern Customisations. #SharePoint, #Office365.. If you're new to the SharePoint Modern UI, you might think "we can't customise this," or that they've closed the door on developers and power users.

While that may have seemed the case up until very recently, from November 2017 there have been some awesome changes to SharePoint Online that enable customisation - even if you're not a developer.

List and Library forms can now be customised in the browser to become PowerApps; cumbersome workflows can be replaced with Microsoft Flows and Flow Approvals; many JSLink and client side rendering customisations can be replaced with JSON Column Custom Formatting.

There's still a lot missing - and right now, only developers can fill in the blanks. Whilst you can still use SharePoint Classic pages for building search solutions, you'll need a developer if you want to build a Modern search experience.
Currently, we build ours using the SharePoint Framework to make Modern Web Parts that use the existing search and graph APIs.

Get in touch if you want to know more.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

14 1

View on Instagram

Link to display lightbox

Instagram post 17893548037163436

#spthingaday 060 - SharePoint Search. Changing the Search Topology. #SharePoint, #SharePointSearch.. The Search Service in SharePoint on-premise is made up of six components.

Crawl, Content Processing, Index, Analytics, Query and Administration.

Each of these components can be placed on one or more servers in your Farm.

To make any one Search component support high availability, you need to make sure there are at least two servers in your Farm running it.

SharePoint Server 2010 had only 3 types of component, and Microsoft let you manage their placement via Central Admin, in the browser.

From SharePoint 2013 onwards, this was deemed too difficult to express graphically.

For SharePoint 2013 and 2016, topology changes need to be made via PowerShell.

Tomorrow, we'll look at just what PowerShell cmd-lets you need to use.

#microsoft #microsoftoffice #microsoftsharepoint #microsofttraining #officetraining #freetraining #trainingvideos #contentmanagement #enterprisecontentmanagement ...

12 0