• A few of initial questions:
  • When did you first notice or was it reported that your "SharePoint" was slow?
  • What did you do?
  • What has been modified?
  • When was it modified?
  • Does your Site Contents page load quickly?
  • Did you compare before and after Network "traces" with F12 developer tools and your browser?
  • Did you compare before and after with Developer Dashboard (if accessible)?

Anti-Patterns (in other words, don't do these things)

• Build custom client-side controls that issue client-side data requests to SharePoint and add a dozen or more of them to the page
  • What has been modified?
  • When was it modified?
  • Did you compare before and after Network "traces" with F12 developer tools and your browser?
  • Did you compare before and after with Developer Dashboard (if accessible)?
• Implement your client-side controls without centralized data access to the SharePoint data, so that numerous controls are requesting exactly the same data numerous times in a page
  • tsk, tsk
• Embed redundant custom JavaScript and CSS throughout the page body
  • If I had a dollar for every time I saw the same libraries loaded multiple times from non-cached locations and then collisions and craploads of stuff, I would have many dollars.
• Embed several 10MB thumbnail images throughout the page body
  • Review your images for optimization for filetype, size, color, etc etc.
• Execute all client-side data requests at page load time, even if the data is not initially needed/displayed, even if it might never be used
  • tsk, tsk
• Inject unnecessary order dependencies into the data request sequence and use synchronous data requests to ensure the order of execution
• Use the legacy SharePoint Lists (SOAP) web service as the data request API of choice and pass it poorly-formed CAML queries
• Avoid caching data responses (especially for static data) on the client to ensure that each data request gets re-executed on every page load
• Perform hundreds of updates to the Document Object Model (DOM) of the page as each data response completes, even if they are redundant or conflicting

• https://powerbi.microsoft.com/
• https://www.youtube.com/user/mspowerbi

• http://www.matthewjbailey.com/highlights-microsoft-data-insights-summit-2017/

First visit if interested should be to the Explore section - http://msdn.microsoft.com/en-US/office/apps/fp123579

1. Introducing a new class of apps
2. Wondering what apps can do?
3. How do apps work, anyway?

Reimagining SharePoint Development - http://msdn.microsoft.com/en-us/office/apps/dn133840.aspx is what made me want to document this and share it. Quick videos to whet your whistle.

Many other videos, training, documents and others.

Apps for SharePoint overview = http://msdn.microsoft.com/en-us/library/office/apps/jj163230.aspx

Enjoy

http://social.technet.microsoft.com/wiki/contents/articles/12409.sharepoint-server-2013-test-lab.aspx "

There are some very good videos and reference materials at the Test Lab Guide Stack for SharePoint Server 2013 link above. Enjoy! 

Beaker reference for those not knowing the Muppets = http://en.wikipedia.org/wiki/Beaker_(Muppet)

Analyzes the following objects from SharePoint solutions (.wsp) for SharePoint 2007 / 2010 / 2013 and SharePoint 2013 apps directly in Visual Studio 2010/2012/2013 

1. Assemblies
2. Memory disposal rules previously checked by SPDisposeCheck
3. XML code in SharePoint packages
1. Features
2. Content Types
3. List Templates 
4. Controls
5. Pages (.aspx) and Master Pages
6. Stylsheets 
7. JavaScript

http://www.spcaf.com/ for additional information on this and additional items.

NOTE : I am not endorsing any products or tools, only sharing some TLC of tools that may help address some common pain points around development, deployment and my beloved and often abused SharePoint.

For example, BOB logs on to the MOSS2007 site collection as DomainA\BOB

However, the company DomainA has been purchased and absorbed by the much bigger company DomainB and they have new logons for BOB. BOB (aka Robert) is a very important author of items in the site collection that is being brought over and is the husband of the CEO of DomainB. He MUST retain his access to the content in the farm being brought over to DomainB via the copy and upgrade of the content database.

Bob now logs on as DomainB\Robert and goes to the new url for his migrated and upgraded site collection. He sees the site, but none of the documents are authored by him. Heck, they all say DomainA\Bob and he can not do anything to the items. Oh oh, he is on the way to see the CEO and you (the SharePoint dude(tte)) just happen to overhear his frustration and yell out "No worries Bob, I can fix it for you."

At a high level, the users for your MOSS 2007 site collection will come over in the content database and you need to do some matching and migrating.

The user in the site collection is DomainA\Bob and he maps to the userID of 231 (just a number I picked, but it is important as it is a number that is Bob) in the users listing on the site. If a site collection admin ADDS DomainB\Robert as a new user, Robert will not be userID 231, but whatever the next userID number is that is available. As such, DomainB\Robert will not have the specific permissions that DomainA\Bob had. In fact, to SharePoint, they are 2 DIFFERENT Users. STOP THAT SCA! OK, you did, let's continue.

As the SharePoint FARM administrator on the SharePoint 2010 farm with permission to the User Profile Service application you can save the day for Robert using MigrateUser from the Get-SPFarm object.

From the SharePoint 2010 Management Shell (YAY PowerShell!)

$SPFarm = Get-SPFarm

$Bob = "DomainA\Bob"

$Robert = "DomainB\Robert"

$IgnoreSIDHistory = $true # different domains, totally different users, SID history would be a little odd.

$SPFarm.MigrateUser ($Bob, $Robert, $IgnoreSIDHistory)

A more in-depth write-up is available at http://blogs.msdn.com/b/sowmyancs/archive/2012/01/07/migrate-users-groups-powershell-script.aspx as the method above is a quick few minutes in PowerShell for one user. Chances are you are going to need to do this for all users.

If you need to update or change any other Properties for DomainB\Robert that are tied to his Active Directory Properties, take a look at http://blogs.msdn.com/b/adpowershell/archive/2009/02/25/ad-powershell-quick-start-guide.aspx

WARNING : I have seen numerous posts on the internet stating that you could/should/would do this with T-SQL. I HIGHLY RECCOMEND THAT YOU DO NOT DO THIS. Unless, you like living on the edge and getting all unsupported. There is really no need to do the direct SQL method anyways, the methods are fairly straight forward.

If you have had the pleasure of upgrading an "inherited" site collection or content database from MOSS 2007, chances are you have had to deal with some errors for a feature or two or more.

The "SharePoint Feature Administration and Clean Up Tool" on codeplex is very helpful is alleviating the pain or discomfort caused by not know who, what, where, when, why or how all them features that failed to load on the 2007 and/or 2010 farm.

Out of the gate, there is a 2007 version to inspect and clean your 2007 SharePoint farm, web application, site collection, or site in a few clicks. By cleaning the 2007 site collections in the content database first, your Mounting of the content database for upgrade to SharePoint 2010 will go much smoother.

I hear the complaints already, but, you have a 2010 site collection that you inherited, can this tool help me clean up the "crap?" Yep! Run the 2010 version on your farm and prune away.

“Each code sample is part of the SharePoint 2010 101 code samples project. These samples are provided so that you can incorporate them directly in your code. Each code sample consists of a standalone project created in Microsoft Visual Studio 2010”

Happy Coding!