IamCalvinBrown.com a Blog Site

Code Examples, Consulting Advice and lots of other cool things

Enable SharePoint Developer Dashboards

SharePoint Developer Dashboards are easy to use and follow. Think of these dashboards as Fiddler Lite. For more information you can go here for SharePoint 2010 and here for SharePoint 2013.

The overall steps to start the Developer Dashboard are

1) If you have not already, configure and enable your Usage and Health Data Collection Service. For more info click here

2) Once you have your app up and running, execute the following PowerShell Script
$svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
$dds = $svc.DeveloperDashboardSettings
$dds.DisplayLevel = "On"
$dds.Update()

3) If everything worked you will see

4) From there you can find out page information, SQL query calls, etc.


An extremely useful tool especially if you are troubleshooting performance.



Hey nothing big … I just need a SharePoint site

A site, just a team site right, no big deal? Such a simple request that causes the beginning of the end for SharePoint environments across organizations. Without a plan of attack, a repeatable plan of attack for your SharePoint sites, what starts off as a small intranet turns into an unmaintainable disaster. So now that I have your attention, the next question is what should be the plan of attack? A SharePoint site request should be treated as any other application request. If there was a request for a complex application, the first thing that would be done is to gather requirements, right? Well the same approach should be taken for any SharePoint requests.

 

Approach to SharePoint Requirement Gathering

Below is are some questions and a good place to start, obviously you can cater for your environment. These questions are designed to do three things:


  • Show the users that SharePoint is more than a document repository and showcase more of
  • Get the users take ownership of the site and decide on a point of contact
  • Assist in minimizing as many risks as possible

 

Question

Response

Business Owner

Portfolio Owner

Budget Holder

Business Objective(s)

Desired Outcome(s)

Number of proposed users

Geography(ies) of proposed users

Will users be internal only, external or both?

What user roles do you expect the solution to accommodate?

Are there any local language requirements associated with this solution?

Are there any specific device platforms you need to support e.g. tablet/mobile?

Will the solution contain secure data (personal, financial or client)?

What type of data do you require the solution to store?

What are the likely volumes of data objects (e.g. documents) to be stored per year and over the lifetime of the solution?

Do you expect the solution to require workflow?

Is data migration required? (Outside of the SharePoint)

Will the solution require integration with another system or data source?

     - If yes, is this integration for inbound, outbound data or both?

     - If yes, what is the name/type/technology of the integration system?

What is the requested Implementation Date?

Why has this date been identified/defined?

Will this replace an existing solution, if so what is the name/platform of that solution?

Will the solution/enhancement consolidate & simplify a current solution/process/activity?

Will the solution/ehnancement improve the delivery of information?

Will the solution/enhancement realise individual/team/business efficiencies?

Describe the new/existing business processes

Will user training be required?

What is the backup procedures?

Is there a Dev, QA, Staging environment?

 

Conclusion

I would be remiss if I did not say that we at King Strategy Solutions specialize in analyzing the proper requirements and determining the best approach from a development perspective.