SammyKailini

Disable or Enable PowerApps, Flows, and Dynamics 365 Tiles from the App Launcher in Office 365

Sammy Kailini MSFT — Wed, 04 Jan 2017 23:54:35 GMT

Here is a sample script that should allow you to enable/disable PowerApps, Flow and the Dynamics 365 Tiles for all users in a tenant by enabling/disabling certain service plans within your enterprise pack.

Before

After

First you need to find the appropriate AccountSKUIds Connect-MsolService Get-MsolAccountSku Second, find the available service plans Get-MsolAccountSku | select -ExpandProperty ServiceStatus Third, Copy/Paste the following PowerShell script. Please supply your values for the Global Admin $user, $Password, $ServicePlans and $AccountSkuId. #Please install the SharePoint client components SDK - https://www.microsoft.com/en-us/download/details.aspx?id=35585 prior to running this script. <#Disclaimer: This Sample Code, scripts or any related information are provided for the purpose of illustration only and is not intended to be used in a production environment. THIS SAMPLE CODE AND ANY RELATED INFORMATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE. We grant You a nonexclusive, royalty-free right to use and modify the Sample Code and to reproduce and distribute the object code form of the Sample Code, provided that You agree: (i) to not use Our name, logo, or trademarks to market Your software product in which the Sample Code is embedded; (ii) to include a valid copyright notice on Your software product in which the Sample Code is embedded; and (iii) to indemnify, hold harmless, and defend Us and Our suppliers from and against any claims or lawsuits, including attorneys’ fees, that arise or result from the use or distribution of the Sample Code.#> #Author:Sammy Kailini, Sammyk@microsoft.com | SammyKailini@live.com Import-Module MsOnline #Configure Site URL and User $User = "admin@Tenant.onmicrosoft.com" $Password = "Password" | ConvertTo-SecureString -AsPlainText -Force #its not recommended to save passwords inside scripts, please save passwords encrypted in a separate file instead. #Service Plans to Disable $ServicePlans = "FLOW_O365_P3","POWERAPPS_O365_P3" $AccountSkuId = "Tenant:ENTERPRISEPREMIUM" #Configure Report Path $ReportPath = "c:\Error_Report.csv" #---------------------Nothing needs editing below this line------------------------------------------------- If (Test-Path $ReportPath){ Remove-Item $ReportPath } #Write Output Report CSV File Headers "User, Error Message" | out-file $ReportPath -Encoding ascii -Append #Add references to SharePoint client assemblies and authenticate to Office 365 site - required for CSOM [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client") [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.Runtime") [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SharePoint.Client.UserProfiles") #Connect to SPO $PSCreds = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList $User,$password Connect-MsolService -Credential $PSCreds $LO = New-MsolLicenseOptions -AccountSkuId $AccountSkuId -DisabledPlans $ServicePlans Write-Host Write-Host "FYI: This could take a while :)" -ForegroundColor Cyan [String]$licenses = $null $users = get-msoluser -All | where {$_.islicensed -eq $true} | select userprincipalname,licenses $progressCount = 0 foreach($usr in $Users) { $progressCount++ Write-Host processing $progressCount out of $users.Count -ForegroundColor Cyan -NoNewline $output += $usr.UserPrincipalName+"," Try { Set-MsolUserLicense -UserPrincipalName $usr.UserPrincipalName -LicenseOptions $LO -Verbose Write-Host " Success, updated user" $usr.UserPrincipalName -ForegroundColor Green } Catch { $ErrorMessage = $_.Exception.Message $output += $ErrorMessage $ErrorMessage } } $output | Out-File $ReportPath -Encoding ascii -Force -Append Write-Host "Done!!" -ForegroundColor White -BackgroundColor DarkCyan Happy SharePointing :) SammyK

How to Troubleshoot Missing Search Item Results Crawled by the Cloud Hybrid Search Service Application

Sammy Kailini MSFT — Fri, 13 May 2016 02:42:37 GMT

While working on a large Cloud Hybrid Search implementation for one of our enterprise customers, we ran into an issue where users can't find certain items and documents when submitting search queries from SharePoint Online!! We have confirmed the users had permissions to these items from the on-premises SharePoint farms and we also have confirmed these individual missing documents have been crawled successfully by the Cloud Hybrid Search Service Application by reviewing the search crawl logs, yet those items still didn't show up when querying from the search center on SharePoint online!! One fact to point out is, when reviewing the crawl logs for the Cloud Hybrid Search Service Application, if an item shows as successfully crawled, then it is. Meaning, we do send an acknowledgement back to the Hybrid Search Service when the item has successfully been added to the SPO index. Best method to confirm the item is actually in the SPO index is to use the Content Search (FKA, Compliance Search) through the Security and Compliance center, that is because the way queries are handled by eDiscovery or Compliance Search are different than just submitting it through the regular search center. We indeed were able to see the missing documents/items through Compliance Search. This confirms the items are for sure in the SPO index, however, users still can't find it through the search center. It became obvious at this point that we are dealing with a security trimming issue, working with my colleague Manas Biswas (Manas has a great multi-part series on how to Configure Hybrid Search check it out), we dumped the ACLs for some of these items we have found two issues:

An Active Directory group securing some of the items has not been synced to Azure AD through the AD Connect Tool. To solve this issue, all security groups securing content on SharePoint On-Prem must be synchronized to Azure AD.
If you are securing Sites/Site Collections/Web Applications on-prem through AD groups or granted direct permissions to individuals, then the root site collection in SharePoint online must have either one of the following permissions:
- Everyone or Everyone Except External Users groups added to it (for example, adding Everyone Except External Users to the visitors group on the root site collection in SPO.
- If you don't want everyone to access to root site collection (the Everyone and Everyone Except External Users Groups have been removed from the root site collection in SPO) then you would need to grant explicit permissions to those AD Groups or individuals to the root site collection in SPO.

In summary, all that we need is users/groups to be present in Azure AD and be permissioned in one or the other way (any security group or explicit user addition ) to the root site collection in SPO either directly or through the Everyone or Everyone Except External Users. Hope this helps anyone that runs through these issues. Happy SharePointing :) Sammy Kailini | Premier Field Engineer | Microsoft

How to get Total Item Count of Externally Crawled Content in SPO with Cloud Hybrid Search Implementation

Sammy Kailini MSFT — Wed, 11 May 2016 19:14:46 GMT

This post is about How to get an accurate item count of your external content crawled through the Cloud Hybrid Search Service Application? I've worked with one of my customers on a larger implementation of Cloud Hybrid Search with SharePoint 2013 and SharePoint Online where the customer is to crawl around 140 TB of content from onprem farms, file shares, LOB..etc. The issue the customer had is they weren't confident they can query all items crawled by the Cloud Hybrid Search farm, because when trying to compare the search results count at the bottom of the search results page when issuing a general query such as isexternalcontent:1 or an asterisk query '*' they will get a fraction of the expected item count!! One note to make is, the search results count at the bottom of the search results page is an estimated count, hence you see About xxxx Results at the bottom of the page!! You will also notice the number of results will change as you page through the results page. This is by design as we only retrieve the most relevant results to the search results page (Can you imagine having to retrieve millions of items all at once and do a count on it!!) mater of fact most popular internet search engines do the same. This is due to pre-set timeouts on the query code that are set by the product group, it doesn't matter if you submit your query through the UI, REST API or the Search Query Tool!! The best way to get a good item count for your crawled external content is by using the Content Search (Compliance Search) through the Security and Compliance Center by submitting a query for isexternalcontent:1 Look for my other blog post if you are experiencing issues querying for external crawled content where the items/documents are missing from the search results page on SharePoint online, How to Troubleshoot Missing Search Item Results Crawled by the Cloud Hybrid Search Service Application Happy SharePointing :) Sammy Kailini | Premier Field Engineer | Microsoft

Office Web Apps 2013 - Increase Excel Workbook Size from the 10 MB Limit

Sammy Kailini MSFT — Wed, 25 Jun 2014 17:18:00 GMT

If you were ever greeted by a message similar to the following:

"Wow, that's a big workbook. Unfortunately, we can't open a workbook larger than 10 MB.

You'll need to open this in Excel."

By default Excel Web App is set to a max size of 10 MB, here are my findings for other Office Web Apps 2013 documents:

Word Docs (no preset/published size limits, however, it is limited by file upload size configured on the SharePoint web application for up to 2GB)
PowerPoint (no preset/published size limits, however, it is limited by file upload size configured on the SharePoint web application for up to 2GB)
Excel Workbooks (Set by default to 10mb size limit, however it can be increased to file upload size configured on the SharePoint web application for up to 2GB)
OneNotes (no preset/published size limits, however, it is limited by file upload size configured on the SharePoint web application for up to 2GB)

The workbook size is controlled by a property ExcelWorkbookSizeMax, to get the current value of this property

Log onto the Office Web Apps 2013 Server > Open PowerShell and type

Get-OfficeWebAppsFarm

To change this value from 10 MB to lest say 50 MB, just execute the following in PowerShell

Set-OfficeWebAppsFarm -ExcelWorkbookSizeMax 50

And there you have it, happy SharePointing :)

What is addressed in SharePoint Server and Office Web Apps 2013 Service Pack 1 (SP1) Update

Sammy Kailini MSFT — Tue, 25 Feb 2014 13:34:00 GMT

Service Pack 1 (SP1) for SharePoint Server and Office Web Apps 2013 was released today Feb 25, 2014. I wanted to do a quick overview and reference what is being addressed in this service pack along with links to where to go to download the appropriate packages. Please note this service pack includes two kinds of fixes:

Previously unreleased fixes that are included in this service pack. In addition to general product fixes, these fixes include improvements in stability, performance, and security.
All the monthly security updates that were released through January 2014, and all the Cumulative Updates that were released through December 2013.

What’s new in SP1?

Compatibility fixes for Windows 8.1 and Internet Explorer 11.
Better support for modern hardware, such as high DPI devices and the precision touchpad.
New apps for Office capabilities and APIs for developers.
Power Map for Excel, a 3D visualization tool for mapping, exploring, and interacting with geographical and temporal data in Excel, is now available to Office 365 ProPlus subscription customers. You can learn more about Power Map general availability on the Power BI Blog.
Improvements to the Click-to-Run virtualization technology that installs and updates Office 365 desktop applications.
SkyDrive Pro is now OneDrive for Business.

For a list of issues that the service pack fixes download this workbook.

Product	KB Number	Details
SharePoint	2817429?	Metadata is lost when documents that use a custom content type with a "Description" field are opened for editing.
SharePoint	2817429?	When an item is deleted, restored from recycle bin, and then deleted again, there is a primary key constraint error.
SharePoint	2817429?	An error occurs when files are moved between document libraries and the web time zone is behind that of the server.
SharePoint	2817429?	Metadata filtering at list level always lists all metadata terms.
SharePoint	2817429?	The hyperlink popup window drops the selected word to be linked when there is a delay of more than one second in opening the window.
SharePoint	2817429?	Multiple-column, SummaryLinkWebParts with a group heading style of "Separator" are rendered incorrectly.
SharePoint	2817429?	A hash tag that contains a full width space does not get created successfully.
SharePoint	2817429?	Search schema compression is now enabled by default to allow larger search schemas.
SharePoint	2817429?	Highlighting for FQL queries is now enabled for FQL as well as KQL.
SharePoint	2817429?	Opening a custom SharePoint list in datasheet view and applying multiple custom filters, where each filter has more than one condition, can result in an incomplete set of list items.
SharePoint	2817429?	When the "Export to Excel" button is clicked in a SharePoint document library that has the Content Type field displayed, the Content Type field does not appear in the Excel workbook.
SharePoint	2817429?	An error occurs after changing the "Manager" property in EditProfile.aspx page when the My Sites WebApp is not in the same farm as the UPA.
SharePoint	2817429?	SharePoint REST API does not return a well-defined error response for a duplicate key exception.
SharePoint	2817429?	Developers are unable to specify a Content Type ID when creating Content Types in the client object model.
SharePoint	2817429?	On list views in SharePoint sites, the Connect to Outlook button in the ribbon may be erroneously disabled.
SharePoint	2817429?	In some non-English languages of SharePoint, the text displayed in the callout UI for a document or list item, describing who last edited the item, may not be grammatically correct.
SharePoint	2817429?	Copy and Paste in a datasheet does not work correctly with Internet Explorer 11.
SharePoint	2817429?	Pages do not render in Safari for iPad when private browsing mode is used.
SharePoint	2817429?	When editing rich text fields in SharePoint, if the editing session exceeds 30 minutes, the edits may not be saved.
SharePoint	2817429?	An error that says "SCRIPT12004: An internal error occurred in the Microsoft Internet extensions" may occur intermittently when users visit their SkyDrive Pro or other pages on their personal site.
SharePoint	2817429?	InfoPath may crash when a form that points to a SharePoint list, with a lookup to another SharePoint list, is opened.
SharePoint	2817429?	An InfoPath form with extended characters in its name fails to open.
SharePoint	2817429?	An error that says "Security Validation for the form has timed out" may occur when an InfoPath form is digitally signed and hosted in a SharePoint site collection that uses the SharePoint version 2010 user experience.
SharePoint	2817429?	"Show document icon" remains unchecked and the document icon does not show in Edit Properties for a list item.
SharePoint	2817429?	A "Failed tagging this page" error occurs when the "I like it" button is clicked.
SharePoint	2817429?	The wrong term is removed when manually editing a multi-valued taxonomy field.
SharePoint	2817429?	When tagging list items using a language that is different from the term store default language, suggestions for labels are offered in multiple languages. The suggestions appear confusing because both language suggestions are listed without any identification of the language.
SharePoint	2817429?	An error that says "There was an error processing this request" may appear when editing the user profile.
SharePoint	2817429?	Times are missing from Date/Time results in certain filtered list web service calls.
SharePoint	2817429?	Minimal and no metadata are now enabled as supported JSON formats.
SharePoint	2817429?	Actions4 schema workflow actions can't be deployed to SharePoint.
SharePoint	2817429?	Using Client Object Model, Stream.Seek() to seek to a particular position doesn't seek at the proper offset.
SharePoint	2817429?	Refreshing a workflow status page generates the following error: "System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary."
SharePoint	2817429?	Setting custom, non-English outcomes in web pages on tasks in a workflow fails to set the value.
SharePoint	2817429?	Configurations of SharePoint using Azure Hybrid mode and Workflow Manager together can cause workflow callbacks to fail.
SharePoint	2817429?	Workflow task processes on wiki pages won't start.
SharePoint	2817429?	Workflows won't wait for changes to content approval status fields.
SharePoint	2817429?	E-mails generated by workflow cannot be disabled for approvals in SharePoint workflows.
SharePoint	2817429?	Workflows may fail to send an e-mail or send too many e-mails.
SharePoint	2817429?	Association variables do not update correctly for auto-start workflows.
SharePoint	2817429?	A KeyNotFoundException error may occur in a workflow when the associated task list uses unique permissions.
SharePoint	2817429?	Incomplete tasks are deleted when workflow task activities complete.
SharePoint	2817429?	Task activity is suspended when the task is completed using app-only credentials.
SharePoint	2817429?	An error that says "This task could not be updated at this time" occurs when trying to complete a workflow task using the "Open this task" button in Outlook.
SharePoint	2817429?	A workflow doesn't respond properly when waiting for changes in specific types of list columns, such as Boolean, Date Time, and User.

Download links to all SP1 updates, download and install the appropriate service packs for the product that you have installed.

Package name	How to obtain the package	Knowledge Base article
Microsoft SharePoint Server 2013 Service Pack 1	Collapse this imageExpand this image Download the 64-bit update now .	2817429 Description of Microsoft SharePoint Server 2013 Service Pack 1 (SP1)
Microsoft Project Server 2013 Service Pack 1	Collapse this imageExpand this image Download the 64-bit update now .	2817434 Description of Microsoft Project Server 2013 Service Pack 1 (SP1)
Microsoft SharePoint Foundation 2013 Service Pack 1	Collapse this imageExpand this image Download the 64-bit update now .	2817439 Description of Microsoft SharePoint Foundation 2013 Service Pack 1 (SP1)
Microsoft SharePoint Server 2013 Language Pack Service Pack 1	Collapse this imageExpand this image Download the 64-bit update now .	2817438 Description of Microsoft SharePoint Server 2013 Language Pack Service Pack 1 (SP1)
Microsoft SharePoint Foundation 2013 Language Pack Service Pack 1	Collapse this imageExpand this image Download the 64-bit update now .	2817442 Description of Microsoft SharePoint Foundation 2013 Language Pack Service Pack 1 (SP1)
Microsoft Office Web Apps Server 2013 Service Pack 1	Collapse this imageExpand this image Download the 64-bit update now .	2817431 Description of Microsoft Office Web Apps Server 2013 Service Pack 1 (SP1)
Service Pack 1 for Duet Enterprise for Microsoft SharePoint and SAP Server 2.0	Collapse this imageExpand this image Download the 64-bit update now .	2817426 Description of Duet Enterprise for Microsoft SharePoint and SAP Server 2.0 Service Pack 1 (SP1)

How to Increase the Maximum Upload Size in SharePoint 2013

Sammy Kailini MSFT — Wed, 06 Nov 2013 17:56:00 GMT

There are so many configuration settings documented elsewhere online to increase the maximum file upload size in order to store large files in SharePoint. Often times, you keep on trying different settings (you may even forget what you have tried and still can't get it to work!!) In this post I will walk you through two simple steps to accomplish this task :)

Change the maximum upload size on the web application level

Central Admin>Application Management>Manage Web Applications> Select the desired web app and click General Settings on the ribbon

Modify the web.config file for the appropriate web application, this is located by default at C:\inetpub\wwwroot\wss\VirtualDirectories\web application name or port

Make a backup copy of the web.config, then open it
Do a Ctrl+f to find this element

Modify the above element to match the following

executionTimeout="999999" maxRequestLength="2048000" requestValidationMode="2.0" />

In the above step we added executionTimeout="999999" and we set the maxRequestLength to what we set the maximum upload size on the web application general settings, which is 2048000 (2000mb * 1024 = 2048000)

And that should be all that you have to do :)

If you run into trouble, you can keep on reading on how you can use the ULS logs to find out more information about the issue.

If you upload a large file to an out of the box web application with default settings, you should expect to get an error. Copy the correlation id of the error and open the ULS logs and you should see the following exception about the Maximum request length exceeded, hence we change the maximum request length in the web.config to the desired amount, in this case it was 2048000.
Now change the maximum request length in the web.config and save the file and try to upload a large file size, you should get another error, copy the correlation id and lets check the uls logs one more time. You should see another exception this time is about the request timed out, hence we added executionTimeout="999999"

I am not a big fan of changing the upload file size to a very large amount due to other implications, for instance large files uploaded to IIS can have a high impact on server memory, also transferring large files over TCP can run into network issues where you may have to re-upload the file again from scratch!! A better option is to use some custom upload manager to stream the upload. My recommendation is to set the file size somewhere between 250-400 mb, unless your business case requires otherwise.

Happy SharePointing!!

How to find the version or build number for an Office Web Apps 2013 Farm

Sammy Kailini MSFT — Fri, 20 Sep 2013 14:18:00 GMT

There are multiple ways to find the OWA 2013 patch or build level:

Use PowerShell

Check the X-OfficeVersion header value, on an Office Web Apps (OWA) or SharePoint server, replace the highlighted owa01 in red with your owa server url and run

(Invoke-WebRequest https://owa01/op/servicebusy.htm).Headers

On Office Web Apps server

Get-Content "C:\ProgramData\Microsoft\OfficeWebApps\Data\local\OfficeVersion.inc"

On an Office Web Apps Server, check the OfficeVersion.inc file located here

C:\ProgramData\Microsoft\OfficeWebApps\Data\local\OfficeVersion.inc

You can also check the X-OfficeVersion header value right from the browser. Please head over to my colleague Tom's blog post here.

Issues and Benefits Implementing SharePoint 2013 using SQL Server 2008 R2 vs SQL Server 2012 SP1

Sammy Kailini MSFT — Sat, 09 Feb 2013 20:10:00 GMT

As many of our customers are getting ready to deploy SharePoint 2013, choosing the appropriate version of SQL is critical!! SQL Server 2008 R2 SP1 is the minimum required version of SQL for a database server in a SharePoint 2013 farm (Hardware and software requirements for SharePoint 2013), however, there are impacts of using SQL Server 2008 R2 If you are deploying the enterprise edition of SharePoint 2013 and you are planning on using Access Services 2013 or some of the Business Intelligence (BI) features as they require SQL Server 2012 SP1. In this blog post I'm gathering information to highlight some of these impacts, and show the benefits of using SQL Server 2012 SP1.

Here is a list of SharePoint 2013 Enterprise Edition Service Applications and components that will require SQL Server 2012 SP1 or maybe impacted if using SQL Server 2008 R2:

Access Services 2013:

Requires:

SharePoint Server 2013 on at least Windows 2008 R2
SQL Server 2012 Standard or SQL Server 2012 Enterprise
SQL Server 2012 Feature Pack Components on the SharePoint Server:

Microsoft SQL Server 2012 Local DB (SQLLocalDB.msi)
Microsoft SQL Server 2012 Data-Tier Application Framework (Dacframework.msi)
Microsoft SQL Server 2012 Native Client (sqlncli.msi)
Microsoft SQL Server 2012 Transact-SQL ScriptDom (SQLDOM.MSI)
Microsoft System CLR Types for Microsoft SQL Server 2012 (SQLSysClrTypes.msi)

The following are the software prerequisites for creating and modifying Access apps:

Access 2013 (required for Access app design)
A web browser (required for viewing and updating data)

Please note Access Services 2010 is there for backward compatibility only!! By default, you cannot create a web database by using Access 2013. However, you can still view and edit a web database that was previously created by using Access 2010 and SharePoint Server2010

For more information, see White Paper: Office 2013--Access Services Setup for an On-Premises Installation

Excel Services Application:

When Excel Services 2013 is deployed with SQL Server 2008 R2, users should be able to interact with basic Excel workbooks in the browser, however, to be able to use the new Excel 2013 features such as advanced data models, an instance of SQL Server 2012 SP1 CTP3 or CTP4 Analysis services is required.

The following table summarizes the different levels of BI features you can choose to install and configure.

Level	Features	Install or Configure
SharePoint Only	Native Excel Services Features	Excel Services and other services included with SharePoint Server 2013.
SharePoint with Analysis Services in SharePoint Mode	Interactive PowerPivot workbooks in the browser	Install Analysis Services in SharePoint mode. Register Analysis Services Server in Excel Services.
SharePoint with Reporting Services in SharePoint Mode	Power View	Install Reporting Services in SharePoint mode. Install Reporting Services add-in for SharePoint.
All PowerPivot Features	Access to workbooks as a data source from outside the farm. Schedule Data refresh. PowerPivot Gallery. Management Dashboard. BISM link file content type.	Deploy PowerPivot for SharePoint 2013 add-in.

Report server and Reporting Services Add-in

SharePoint 2013, can ONLY use the SQL Server 2012 SP1 version of the Report Server and Reporting Services add-in for SharePoint. For more info see Supported Combinations of SharePoint and Reporting Services Components.

Power View in SharePointServer 2013

Requires SQL Server 2012 Service Pack 1 (SP 1) editions that enable Power View and Silverlight 5. See System requirements for Power View

PowerPivot for SharePoint 2013

SQL Server 2012 SP1: To be able to use the new Excel 2013 features such as advanced data models on SharePoint Server 2013, an instance of SQL Server 2012 SP1 CTP3 Analysis Services must be installed in SharePoint deployment mode.

As we can see if you need to deploy Access Services 2013 or take full advantage of the new features of the BI stack, you will need SQL Server 2012 SP1. SQL Server 2012 SP1 offers many new features such as SQL Server Backup and Restore with the Windows Azure Blob Storage Service, and Cross-Cluster Migration of AlwaysOn Availability Groups in addition to the following enhanced SharePoint BI features, here is an excerpt from What is new in SQL Server 2012 for SharePoint 2013 BI TechNet article.

What’s new In SQL Server 2012 SP1 for Business Intelligence (With Office and SharePoint Server 2013)

Enable self-service BI as a natural part of users day-to-day activities in Excel 2013:
Access and mash-up data from any source (PowerPivot). Documentation related to PowerPivot in Excel 2013(https://go.microsoft.com/fwlink/p/?LinkID=255958).
Stunning visualizations and data discovery (Power View). Documentation related to Power View in Excel (https://go.microsoft.com/fwlink/p/?LinkID=255957).
Work with hundreds of millions of rows of data (powered by xVelocity in-memory technologies).
Discover, assess and audit user created spreadsheets via SharePoint Server 2013 Preview.
A new version of the Reporting Services add-in for SharePoint and an updated SharePoint mode report server that supports SharePoint 2013. For more information, see the following:

The "SQL Server 2012 Service Pack 1 (SP1)" section of What's New (Reporting Services).
Supported Combinations of SharePoint and Reporting Services Components .

A new architecture for SQL Server 2012 SP1 PowerPivot that supports a PowerPivot server outside a SharePoint 2013 farm. A Windows Installer package (spPowerpivot.msi) that enhances the PowerPivot for SharePoint experience. Additional features include PowerPivot Gallery, schedule data refresh, and management dashboard. For more information, see the following:

The "SQL Server 2012 Service Pack 1 (SP1)" section of What's New (Analysis Services).
Install Analysis Services Server in SharePoint Mode for SharePoint 2013 (SQL Server 2012 SP1) .

Share and collaborate on self-service BI assets via SharePoint Server 2013 Preview and SQL Server 2012 SP1.

Summary:

In summary, If you are serious about the BI features of SharePoint 2013 and the power of the new Access Services 2013 Service Application, you will need SQL Server 2012 SP1. This is how I look at it, you’ll have to upgrade off SQL 2008 R2 at some point, why not skip a migration and start on SQL Server 2012 SP1!!

Resources:

Software requirements for business intelligence in SharePoint Server 2013

What’s new In SQL Server 2012 SP1 for Business Intelligence (With Office and SharePoint Server 2013)

SQL Server BI Features with SharePoint 2013

System requirements for Power View

Supported Combinations of SharePoint and Reporting Services Components.

White Paper: Office 2013--Access Services Setup for an On-Premises Installation