Authentication, authorization, and security in SharePoint 2013

What's new in SharePoint 2013 for authentication, authorization, and security

The following are some of the enhancements added to SharePoint 2013 Preview:

• User sign-in
• Services and app authentication

What's new in authentication for SharePoint 2013 Preview

SharePoint 2013 Preview includes improvements in claims infrastructure and authentication features that enable new server-to-server and app authentication scenarios.

SharePoint 2013: Claims is the new black

In SharePoint 2010, we had to choose between two options when creating a Content Web Application - to use Classic mode Authentication or Claims-based Authentication. Now in SharePoint 2013, Claims-based authentication mode is the default authentication method. You cannot from the web interface create content web applications using Classic mode. Classic-mode authentication is deprecated and can be managed only by using Windows PowerShell.

The app authentication and server-to-server authentication features of SharePoint 2013 Preview require claims-based authentication along with a lot of other features.

Plan authentication in SharePoint 2013 Preview

Find resources about user authentication, server-to-server authentication, and app authentication to help you understand and plan for authentication in SharePoint 2013 Preview.

Configure SAML-based claims authentication with ADFS in SharePoint 2013 Preview 

Describes the steps to configure Security Assertion Markup Language (SAML)-based claims authentication using Active Directory Federation Services (AD FS) 2.0.

Configure forms-based authentication for a claims-based web application in SharePoint 2013 Preview

Describes the steps to configure forms-based authentication using a Lightweight Directory Access Protocol (LDAP) membership provider.

Configure server-to-server authentication in SharePoint 2013 Preview

Provides steps to configure server-to-server (S2S) authentication with another server that uses the S2S protocol.

Initial deployment administrative and service accounts in SharePoint 2013

Information about the administrative and service accounts that are required for an initial SharePoint 2013 deployment.

People Picker and claims providers overview (SharePoint 2013)

Get an overview of People Picker and links to topics about how to plan for People Picker in SharePoint 2013.

Report Where and How SharePoint Users Have Been Granted Access

This script produces a text file report of which items have been unique secured and which Active Directory users and groups have been granted access, based on the user domain specified. The report details whether the user or group has been granted rights directly, or if the user has been granted rights by membership to a SharePoint group though it  does not identify if a user has been granted rights based on their membership to an AD Group which in turn has been added to a SharePoint group.

How to: Deploy a claims provider in SharePoint 2013

Learn how to deploy a SharePoint 2013 claims provider by using the features infrastructure

What's new in SharePoint 2013 upgrade

SharePoint 2013 includes new upgrade features, such as upgrade for service applications, a site health checker, and upgrade for site.

SharePoint 2013 does not support in-place upgrade for an existing environment. You must use the database-attach upgrade method to upgrade your databases to a new environment that is based on SharePoint 2013. Also, to provide more flexibility to farm administrators and site administrators, the upgrade process has changed to separate upgrade of the software and databases from upgrade of the sites.

SharePoint Foundation 2013 known issues

A list of important facts along with known issues and solutions for SharePoint Foundation 2013.

SharePoint Server 2013 known issues

Known issues and solutions for SharePoint Server 2013 and Microsoft SharePoint Designer 2013.

Upgrading from SharePoint 2010 to SharePoint 2013 Step-by-Step

Troubleshoot database upgrade issues in SharePoint 2013

List of common issues and describes general principles to help you identify and address upgrade issues. After you identify and address the issues, you can resume upgrade. Learn how to address problems that may occur after you upgrade a database to SharePoint 2013.

Troubleshoot site collection upgrade issues in SharePoint 2013

When you upgrade a site collection to SharePoint 2013, errors can occasionally occur. Learn how to address problems that may occur after you upgrade a site to SharePoint 2013.

Clean up an environment before an upgrade to SharePoint 2013

Before you start to upgrade from SharePoint 2010 Products to SharePoint 2013, make sure that your environment is functioning in a healthy state and clean up any content that you do not have to upgrade. Also take the time to remove or rearrange content. Make sure that your environment is in a healthy state, and delete unnecessary items before you upgrade to SharePoint 2013.

SharePoint 2013 (Technical Preview) MySite Upgrade and Profile Photos

Upgrade service applications to SharePoint 2013

Upgrade the service applications (Business Connectivity Services, Managed Metadata, Secure Store, User Profiles, Search) to SharePoint 2013. When you upgrade from SharePoint 2010 Products to SharePoint 2013, you must use a database attach upgrade, which means that you upgrade only the content for your environment and not the configuration settings. After you have configured the SharePoint 2013 environment, and copied the content and service application databases, you can upgrade the service applications to SharePoint 2013.

Capacity management and sizing overview for SharePoint Server 2013

This article provides an overview of how to effectively plan and manage the capacity of SharePoint Server 2013 environments. This article also describes how to maintain a good understanding of the capacity needs and capabilities of your deployment, by analysis of performance and volume data. It also reviews the major application impacts that affect capacity, including content characteristics and usage.

Capacity management and sizing for SharePoint Server 2013

Learn about the concepts and planning considerations for managing the capacity of a SharePoint Server 2013 environment and helps you to make the decisions regarding the appropriate capacity for your SharePoint Server 2013 environment.

Software boundaries and limits for SharePoint 2013

This article describes software boundaries and limits of SharePoint Server 2013 along with the tested performance and capacity limits of SharePoint Server 2013 and how limits relate to acceptable performance.

SharePoint and Database Statistics: Why are they out-of-date and what to do about it

Interesting insight about the database maintenance job which runs every night. However, there are chances that the update statistics operation will be skipped without any indications in the ULS logs. The article sums up the findings and the recommendation to ensure that database statistics are updated at least daily.

Introduction to Shredded Storage in SharePoint 2013

Shredded storage is a new data platform improvement in SharePoint 2013 related to the management of large binary objects (I.e. BLOBS such as Microsoft PowerPoint Presentations, Microsoft Word Documents, etc.). At its most basic, Shredded Storage is designed to ensure the write cost of updating a document is proportional to the size of the change, and not of the file itself.

Shredded Storage is both improves I/O and reduces compute utilization when making incremental changes to document or storing documents in SharePoint 2013. Shredded Storage builds upon the Cobalt (I.e. File Synchronization via SOAP of HTTP) protocol introduced in SharePoint 2010.

Digital asset library planning in SharePoint Server 2013

SharePoint Server 2013 provides an asset library which is special kind of document library. It lets you store and manage digital assets — such as images, audio, video, and other reusable content fragments from many applications— that is shared with other site users. Content types that are designed specifically for audio and video assets support the storage and playback of those assets in Web Parts and Web Part pages, and the HTML5 player is integrated with the user interface to enhance the media playback experience for users. Use the articles in this section to guide you in planning the management of digital assets in a solution that is based on SharePoint Server 2013.

Plan digital asset library topology and architecture in SharePoint Server 2013

Learn about logical architecture and topology decisions that are related to deploying digital asset libraries.

OAuth 2.0 and Sign-In

OAuth 2.0 is NOT an authentication protocol. The OAuth 2.0 protocol is aimed at authorizing rather than authenticating and its aim is to authorize applications. OAuth 2.0 is an authorization framework. OAuth 2.0 cannot be used to implement a sign-in flow without adding provider-specific knowledge. Read this post from Vittorio Bertocci to know more.

Viewing reports and dashboards on mobile devices

This article contains detailed information about how to create reports, scorecards, and dashboards that can be viewed by using a mobile device, such as Apple iPad and Windows 8 tablets. Learn how to view reports and dashboards on mobile devices, such as Apple iPad and Windows 8 tablet devices.

What's new for mobile devices in SharePoint 2013

SharePoint Server 2013 offers new, optimized viewing experiences across different mobile platforms. Additionally, several new features were added to help improve both worker productivity and usability on the device. In this article, you can learn about the new mobile features available in SharePoint Server 2013, including the mobile browser experience, device channels, and location.

Configuring business intelligence content for viewing on mobile devices

This article contains recommendations on how to configure business intelligence content to display on devices such as Apple iPad or Windows 8 slate (or Surface) devices. Learn tips and tricks of configuring reports, scorecards, and dashboards to be displayed correctly on mobile devices.

What's new in search in SharePoint Server 2013

Learn about new search capabilities in SharePoint Server 2013, including ways to configure and monitor the system and improve search results.

SharePoint 2013 uses the web-based interface to show the current status of the topology. However, unlike SharePoint Server 2010 that included a web-based option for changing the topology along with Windows PowerShell, SharePoint 2013 does not include the option to change the topology from the web-based interface.

Manage the Search Center

Learn about pages that are created in a Search Center site in SharePoint Server 2013, and see articles about how to configure Web Parts. When you create an Enterprise Search Center site collection, SharePoint 2013 creates a default search home page and a default search results page. In addition, several pages known as search verticals are also created. Search verticals are customized for searching specific content, such as People, Conversations, and Videos, and they display search results that are filtered and formatted for a specific content type or class.

Manage continuous crawls in SharePoint Server 2013

Learn how to enable continuous crawls of SharePoint content to help keep the search index and search results as fresh as possible. Enable continuous crawls is a crawl schedule option that is new in SharePoint 2013. It is available only for content sources that use the SharePoint sites content source type. A continuous crawl starts at set intervals. The default interval is 15 minutes, but you can set continuous crawls to occur at shorter intervals by using Windows PowerShell.

Apps for SharePoint overview

Learn what apps for SharePoint are, why you should build them, and the concepts that are fundamental to building them in SharePoint 2013 Preview.

Plan for apps for SharePoint 2013

The apps for SharePoint provide a new method to deliver specific information or functionality to a SharePoint site. An app for SharePoint is a small, easy-to-use, stand-alone productivity app that solves a specific end-user need. Learn how to use apps for SharePoint 2013. Plan the App Catalog, app URLs, and how to monitor and license apps.

Overview of profile synchronization in SharePoint Server 2013

The process of importing profile data from external systems and writing data back to these systems is called profile synchronization. Learn about profile synchronization, also known as "profile sync," in SharePoint Server 2013.

Microblog features, feeds, and the Distributed Cache service overview in SharePoint Server 2013

Learn about microblog features, newsfeed, and the Distributed Cache service in SharePoint Server 2013 Preview.

For IT Pro - Capabilities and features in SharePoint 2013

SharePoint 2013 training for IT pros

How-to training and walkthrough videos with this interactive course about SharePoint 2013 including changes and new features for search, social, deployment and performance/scalability.

What’s new for developers in SharePoint 2013 

Developer Training

SharePoint 2013 Top 10 New Features

Overview of the Top Features of SharePoint 2013

The New SharePoint

Highlights of the new version of SharePoint

New SharePoint Technical Content

The TechNet home page and feature package covers IT professional content for new Office, Office 365, SharePoint, Exchange, Lync, and Project

SharePoint 2013 Technical Library in Compiled Help (Chm)

CHM version of SharePoint 2013 content in the SharePoint 2013 technical library.

I had a requirement from customer to develop an archival workflow solution using which they can automate the Site Collection archival based on a set of business rules. The features should be, notify users for the key LOB information expiration based on which the sites were created, Maintain the notification count and based on the count take a call to make a particular site read-only, offline or take a back up & delete it permanently from the content database in case of no action taken to update the key LOB information.

And, just to give you a little idea about the size of the farm, it’s in TBs and there are thousands of site collections created automatically across multiple content databases through an automated process. so to do the above steps manually for each site collection based on different notification counter values and repeat it every week, was just impossible and that’s how we decided for an automatic site archival solution.

The purpose of this blog post is to give you an idea about the various features and parts of the solution so in case you come across any of the similar business requirement in future then can make use of some of these ideas or code snippets and make your life little easier

This solution has several features like

1. Automatic scanning for all Site Collections with expired Key Information(Based on which Site Collections are created)
2. Check for the expiration date of Key Information with LOB system(The Origin place of the Key Information)
3. Find out the Site Owners
4. Validation of the Site Owners with the directory services
5. Send configurable email notifications to Site Owners about the Key Information expiration
6. Keep track of notifications count
7. Automatically extend the Site Collection’s Key Information details in SharePoint if it’s been updated in LOB system
8. Make the Site Collection offline based on the notification count in case of no response from Owners
9. Take the Site Collection Backup, transfer the back up to a shared location for the archival & delete it to reclaim the used space based on the notification count
10. Provision to take an exception for a Site Collection for the Key Information expiration scan & archival

And following are the configuration features of the solution

1. Configurable LOB pointer & Workflow Admins list
2. Configurable Email Templates for notifications
3. Configurable Execution Timing/Schedule
4. No IISRESET/ App pool recycle required
5. Logging of each execution in the event viewers for the Admin review

So here is how I designed these configuration features

For Configurable LOB pointer & Workflow Admins list, I kept txt files with solution which would contain the connection and Administrator details respectively so can be modified anytime.

Created XML for the email templates and would read the specific template from the code using template id.

Built whole application as an exe so can be configured with windows task scheduler.

Since no deployment of WSP to SharePoint and solution is just a stand alone exe, no IISReset/ App Pool Recycle required.

Used Event viewer for writing the execution log.

Now following are a few Code Snippets which are used for the above functionalities.

For txt read

try

{

    const string f = "ConnectionString.txt";

    using (StreamReader r = new StreamReader(f))

    {

        connectionString = r.ReadLine();

    }

}

catch (Exception ex)

{

    WritetoEventViewer("Exception(ConnectionString Fileread) : " + ex.Message.ToString());

}

To check user validity with directory services

static bool checkValidUser(string UserID)

{

    bool isValid = false;

    try

    {

        using (var ctx = new PrincipalContext(ContextType.Domain)) 

        {     

            var user = UserPrincipal.FindByIdentity(ctx, UserID);      

            if(user != null)     

            {

                isValid = true;

                user.Dispose();     

            } 

        } 

    }

    catch (Exception ex)

    {

        WritetoEventViewer("Exception(Checking AD User Validation) : " + ex.Message.ToString());

    }

    return isValid;

}

static void GetMailTemplates()

{

    mailTemplates = new string[3, 5];

    try

    {

       int i = -1, j = 0;

        XmlTextReader reader = new XmlTextReader("EmailTemplates.xml");

        while (reader.Read())

        {

            if ((reader.NodeType == XmlNodeType.Element) && (reader.Name == "template"))

            {

                i++;

                j = 0;

                //to save from array overload

                if (i == 2)

                    break;

            }

            if (reader.NodeType == XmlNodeType.Text)

            {

                mailTemplates[i, j] = reader.Value.ToString().Trim('\n', '\r', ' ');

                j++;

            }

        }

    }

    catch (Exception ex)

    {

        WritetoEventViewer("Exception(Getting Mail Templates) : " + ex.Message.ToString());

    }

}

To make NoAccess to the Site Collection

bool operation = false;

try

{

    using (SPSite site = new SPSite(url))

    {

        site.WriteLocked = true;

        site.LockIssue = "Making site collection NoAccess as per the Archival Workflow";

        site.ReadOnly = true;

        site.ReadLocked = true;

        operation = true;

    }

}

catch (Exception ex)

{

    operation = false;

    WritetoEventViewer("Exception(Making SiteCollection Offline) : " + ex.Message.ToString());

}

To backup & move the Site Collection in a shared location

bool operation = false;

try

{

    string bkLocation = @"c:\";

    string bkFileName = DateTime.Now.ToString() + ".bak";

    bkFileName = bkFileName.Replace("/", "");

    bkFileName = bkFileName.Replace(":", "-");

    using (SPSite site = new SPSite(url))

    {

        SPWebApplication webApp = site.WebApplication;

        SPSiteCollection siteCol = webApp.Sites;

        siteCol.Backup(url, bkFileName, true);

        //Move the file to destination after creation

        File.Move(bkFileName, bkLocation + bkFileName);

        operation = true;

    }

}

catch (Exception ex)

{

    operation = false;

    WritetoEventViewer("Exception(SiteCollection Backup) : " + ex.Message.ToString());

}

To delete Site Collection

bool operation = false;

try

{

    using (SPSite site = new SPSite(url))

    {

        //Making site accessible if it is made NoAccess

        site.WriteLocked = false;

        site.ReadOnly = false;

        site.ReadLocked = false;

        //Delete the site

        site.Delete();

        operation = true;

    }

}

catch (Exception ex)

{

    operation = false;

    WritetoEventViewer("Exception(SiteCollection Deletion) : " + ex.Message.ToString());

}

Here I have mentioned the code which can be useful to get the Content DB, Site Collection Usage details.

SPFarm farm                 = SPFarm.Local;

SPWebService service        = farm.Services.GetValue<SPWebService>("");

string webappName       = "";

SPWeb web               = null;

SPUserCollection owners = null;

string OwnerString      = "";

int count               = 0;

foreach (SPWebApplication webapp in service.WebApplications)

{

    webappName                                  = webapp.Name.ToString();

    SPContentDatabaseCollection DBCollection    = webapp.ContentDatabases;

    foreach (SPContentDatabase contentDB in DBCollection)

    {

        //ContentDB details 

        row = null;

        row = tableDB.NewRow();

        row[col1] = webappName;

        row[col2] = contentDB.Name.ToString();

            //Get the ContentDB size from farm database server

            SqlConnection con   = new SqlConnection(contentDB.DatabaseConnectionString.ToString());

            SqlCommand com      = new SqlCommand("select Sum(size/128) from sys.database_files", con);

            try

            {

                con.Open();

                row[col3] = Convert.ToInt64(com.ExecuteScalar());

                con.Close();

            }

            catch (Exception ex)

            {

                WritetoEventViewer("Exception(ContentDB size calculation from farm DB) : " + ex.Message.ToString());

            }

            finally

            {

                con.Dispose();

            }

        row[col4] = Convert.ToInt64(contentDB.CurrentSiteCount);

        row[col5] = Environment.MachineName;

        tableDB.Rows.Add(row);

        //Site collection details

        foreach (SPSite site in contentDB.Sites)

        {

            try

            {

                rowSite = null;

                rowSite = tableSite.NewRow();

                rowSite[Server]         = Environment.MachineName;

                rowSite[WebApp]         = webappName;

                rowSite[ContentDBName]  = contentDB.Name.ToString();

                rowSite[URL]            = site.Url.ToString();

                rowSite[Size]           = site.Usage.Storage; // in bytes

                rowSite[Quota]          = site.Quota.StorageMaximumLevel; // in bytes

                    //Get the Users from site collection's owner group

                    OwnerString = "";

                    web         = site.RootWeb;

                    if (web.AssociatedOwnerGroup != null)

                        owners = web.AssociatedOwnerGroup.Users;

                    if ((owners != null) && (owners.Count > 0))

                    {

                        count = 0;

                        foreach (SPUser user in owners)

                        {

                            string loginname = user.LoginName.ToString();

                            //To remove extra characters from claims

                            if(loginname.IndexOf("i:0#.w|") >= 0)

                                loginname = loginname.Replace("i:0#.w|", "");

                            if (count == 0)

                            {

                                OwnerString = loginname;

                                count++;

                            }

                            else

                            {

                                count++;

                                OwnerString = OwnerString + "; " + loginname;

                            }

                        }

                    }

                rowSite[Owner]          = OwnerString;

                rowSite[ReadLocked]     = site.ReadLocked;

                rowSite[ReadOnly]       = site.ReadOnly;

                rowSite[CurrentResourceUsage] = site.CurrentResourceUsage;

                rowSite[WriteLocked]    = site.WriteLocked;

                rowSite[UsageBandwidth] = site.Usage.Bandwidth;

                rowSite[UsageHits]      = site.Usage.Hits;

                rowSite[UsageVisits]    = site.Usage.Visits;

                tableSite.Rows.Add(rowSite);

            }

            catch (Exception ex)

            {

                WritetoEventViewer("Exception(Site Collection details collection) : " + ex.Message.ToString());

            }

            finally

            {

                owners = null;

                if (web != null)

                    web.Dispose();

                if (site != null)

                    site.Dispose();

            }

        }

    }

}

In this post we will look into how I did “Farm Content Size Reporting” part of the project,

We have two types of reporting in this functionality.

1. Content Databases per Web Applications Report
2. Site Collections per Content Databases Report

This can be useful for a very large size farm and where there could be multiple databases per Web Applications and many Site Collections in each Content Database. This kind of reporting/data is not available OOTB so I developed my own custom utility using SharePoint Object Model which can pull the size data from the farm and can log it into my custom database. I can connect to my custom logging database from my SQL Business Intelligence Project and have the Reports created the way I want. Utility I can schedule on any of the servers in the farm and that can keep pushing the reporting data in my DB. And, at SQL side we can schedule a SQL job which can flush the reporting data from the DB before our utility pushes the new data per the defined schedule.

Content Databases per Web Applications Report

Site Collections per Content Databases Report

For my custom DB, I created two tables in my custom DB as below

Report_SiteCollectionDetails

Report_SiteCollectionDetails

Now that we have got the structure of the reporting and how the components can be integrated, in my next post I will mention a few code snippets to get Content DB & Site Collection size details using SharePoint Object Model.

Continuing from the Post 1,

Request Workload / Agent

Query :

SELECT     

        AgentName, SUM(RequestCount) AS RequestsCount

FROM         

        RequestWorkload

WHERE     

        (LogTime BETWEEN GETDATE() - 10 AND GETDATE()) 

        AND 

        (AgentName IN ('Browser', 'Collab', 'ExcelViewer', 'DAV', 'Groove14', 'Excel14', 'Word14'))

GROUP BY 

        AgentName

ORDER BY 

        RequestsCount DESC

Request Duration / Agent

Query :

SELECT     

        TOP (10) AgentName, SUM(Duration) AS Durations

FROM         

        RequestWorkload

WHERE     

        (LogTime BETWEEN GETDATE() - 10 AND GETDATE()) 

        AND 

        (AgentName IN ('Browser', 'Collab', 'ExcelViewer', 'DAV', 'Groove14', 'Excel14', 'Word14'))

GROUP BY 

        AgentName

ORDER BY 

        Durations DESC

UI & Packaging

For UI, I have used SQL Reporting services since I wanted to make this as a web based solution rather than any thick client application so it can be accessed by anyone(based on the permissions) at any place. I created a project using SQL Server Business Intelligence Development Studio and hosted it in SharePoint. For setting up reporting services with SharePoint, please refer Configuring Reporting Services for SharePoint 2010 Integration.

Also, You may use any of the other methods for reporting like, SharePoint chart controls, Business Connectivity Services(BCS), Custom web parts using ASP.Net chart controls etc…

Thank you for Reading!

In this post, I will talk about my SharePoint Performance Dashboard Project. It has mainly two major types of reporting features, Part 1.  CPU Monitor, Memory Monitor, Top Users of the farm, Top Site Collections in the farm and many more and Part 2. List of content database with the size - for each web application, per content database how many site collections are there and what is the quota of each site collection and how much is used out of it.

So this project was planned in two parts, 1. Server Performance Reporting 2. Farm Content Size Reporting

Considering the length of the information,  I will divide each part into two posts, so lets start with Part 1. Server Performance Reporting

For this functionality, We wanted mainly five types of reporting

1. CPU trend in SharePoint servers in the farm for last 10 days
2. Memory trend in SharePoint servers in the farm for last 10 days
3. Top users of the farm
4. Top Site Collections of the farm
5. Tools used for the access

To begin with, I did my initial research in SharePoint’s Usage and Health data collection functionality. I studied how this functionality is and what type of information it collects. For more information about this functionality, please refer to Configure usage and health data collection (SharePoint Server 2010)

In WSS_Logging database, we have various views available and it really contains very useful information, it’s the data source for our reporting in this part.

Also, I evaluated SharePoint Diagnostic Studio 2010 (SPDiag 3.0) (SharePoint Server 2010). Based on it and by checking the various views from WSS_logging database I could derive all the necessary SQL queries that are required to get various performance information about each server in the farm.

CPU Monitor :

Query :

SELECT     

    MachineName, LogTime, Value

FROM         

    PerformanceCounters

WHERE    

(counterid in 

    (select id from PerformanceCountersDefinitions 

    where 

    category = 'Processor'

    and Machine in ('sharepoint') –- Add your server names of the SharePoint farm here

    )

) 

and (LogTime between GETDATE() - 10 and GETDATE())

order by Machinename,logtime

Memory Monitor

Query :

SELECT 

    LogTime,    [MachineName], [CounterId]

    ,(convert(decimal(10,1),((14336-[Value]) / 1024)) / 14) * 100 'Value'

FROM 

    [PerformanceCounters]

where 

CounterId in (    select id from PerformanceCountersDefinitions 

        where 

        category = 'Memory'

        and 

        Machine in ('sharepoint') –- Add your server names of the SharePoint farm here 

) 

and (LogTime between GETDATE() - 10 and GETDATE())

order by [MachineName],[LogTime]

Top Users of the farm

Query :

SELECT     

         TOP (10) [Username], SUM(RequestCount) AS 'RequestCount'

FROM         

         TopUserRequestCount

WHERE     

         (LogTime BETWEEN GETDATE() - 10 AND GETDATE()) 

GROUP BY UserName

ORDER BY 'RequestCount' DESC

Top URL/Site Collection Requests

Queries :

SELECT  top 10   

    SUM(duration) AS requests, 

    SiteUrl AS Url

FROM         

    RequestUsage

where 

    (LogTime between GETDATE() - 10 and GETDATE())

    and SiteUrl not like '%_vti_bin%'

    and SiteUrl not like '%.axd%'

    and SiteUrl not like '%.asmx%'

    and SiteUrl not like '%office_viewing_service_cache%'

    and SiteUrl not like '%_layouts%'

GROUP BY 

    SiteUrl

order by 

    requests

SELECT top 10

    Url,

    count([Count]) Visitcount

FROM 

    [UrlVisit]

where 

    (LogTime between (GETDATE() - 10) and GETDATE())    

    and Url not like '%_vti_bin%'

    and Url not like '%.axd%'

    and Url not like '%.asmx%'

    and Url not like '%office_viewing_service_cache%'

    and Url not like '%_layouts%'

group by 

    Url

order by 

    Visitcount desc

Information about the other reporting and how I did the UI part & packaging, I have covered in my next post.