Calling SharePoint 2013 REST api using an AngularJS Service

Calling the SharePoint 2013’s REST api can be a repetitive task. During the last Office365 summit in Amsterdam, the developer track always pointed to the Office365 Patterns and Practices for samples on how to develop in office 365. To my greatest joy they also have an SPA sample!

AngularJS services provide a way to share code within the app. This is great for not always having to write the same code over and over again. In this case calling SharePoint REST urls using $http.

The following is a snippet from

(function (angular) {
    "use strict";

        .module('sharepointproxy.service', [])
        .factory('SharepointProxyService', SharepointProxyService);

    function SharepointProxyService($http) {

        var proxyEndpointOptions = {
            url: 'api/sharepoint',
            method: 'POST',
            data: {}

        var defaultProxyOptions = {


        var service = {
            transformRequest: transformRequest,
            sendRequest: sendRequest,
            getWebTitle: getWebTitle

        function getData(o) {

        function transformRequest(request) {
            var transformedRequest = proxyEndpointOptions;
   = request;

            return transformedRequest;

        function sendRequest(request) {
            return $http(request)
                .then(function (data) {
                    return data;

        return service;

    SharepointProxyService.$inject = ['$http'];


It’s a great example on how to start using an AngularJS service calling SharePoint. It can be easily extended with more defined methods, like getting the title of the hostWeb:

        function getWebTitle(hostWebUrl) {
            var requestUrl = hostWebUrl + '/_api/web/title';
            var request = {
                url: requestUrl,
                method: 'GET',
                headers: {
                    Accept: 'application/json;odata=verbose'
            var spRequest = transformRequest(request);
            return sendRequest(spRequest);

All you need to add in your controller is a simple call to the service passing the hostWebUrl:

var queryParameterString = ([0] === '?') ? :;
$scope.queryParameters = deparam(queryParameterString);

        $scope.requestServiceData = function () {
            console.log("Request service data!");
            var result = SharepointProxyService.getWebTitle($scope.queryParameters.SPHostUrl)
            .then(function (data) {
                $scope.serviceResponse = data;

Finish off by adding a button to your HTML to call the service:

<button ng-click="requestServiceData()">Request</button>

Updated SharePoint Query Correlation ID Central Admin Page to 2013

Thanks to Ghislain Lerda, the SharePoint Query Correlation ID Central Admin Page has been migrated to 2013. There’s also a new functionality available on the results page which allows you to export the results to a txt file.

export to txt

export to txt result

The source of the project on CodePlex has been restructured to 2 branches: one for SharePoint 2010 and one for SharePoint 2013. You’ll find future changes for both projects on the same CodePlex site.

You can get the latest at the releases page on CodePlex:

The deployment and configuration of the solution is still the same. Simply install the .wsp on your farm and check the Monitoring category page in central admin. You’ll find a link to the search page there.

High SQL Server CPU usage after SharePoint 2013 Preview install

So I was fiddling around with SharePoint 2013, and everything on my workstation seemed rather slow. I checked the task manager and my SQL Server was consuming so many CPU power, like all the time.

Task Manager_High_SQL_Server_CPU

Checking the resource monitor didn’t show much, so I had to dig down deeper. I fired up my SQL Server Management Studio and copy pasted the following query:

FROM sys.dm_exec_requests a
OUTER APPLY sys.dm_exec_sql_text(a.sql_handle) b
WHERE session_id > 50
and session_id <> @@spid

When you check out the text column, you’ll see lots of queries being executed like “CREATE PROCEDURE”.

sql query results

If you check the ULS logs you’ll see a lot of “slow queries” and when you check your SQL logs, you’ll see lots of warnings about insufficient memory available and that paging slows down your queries. Well, it does. If you’re on a “low memory” machine (I’m running on a virtual machine with 6GB) it’s best to give your SQL server some air. Navigate to your SQL Server properties:

sql server properties

Configure a minimum amount of memory (default is 0):

sql server memory

And boost your SQL Server’s priority:

boost sql priority