Sladescross's Blog

Blogging about Sharepoint related stuff

Office 2013 and PowerPivot and PivotTable November 29, 2013

I will be introducing the new Data Model and Relationships features that will
hopefully change the way you use Excel for data analysis forever.

To modify or manage the Data Model, use the Power Pivot add-in. The add-in is part of the Office Professional Plus edition of Excel 2013, but not enabled by default. More about Start Power Pivot in Microsoft Excel 2013 add-in.


A Data Model is a new approach for integrating data from multiple tables, effectively building a relational data source inside an Excel workbook. Within Excel, Data Models are used transparently, providing tabular data used in PivotTables, PivotCharts, and Power View reports.

Use the Data Model in Power View

A Data Model is used as the basis of a Power View report. Using the Power Pivot add-in, you can apply optimizations to the model that improve Power View reporting. Optimizations include: specify a default field list, choose representative fields or images to uniquely identify specific rows, or specify how rows with repeating values (such as employees or customers with the same name) are handled in a reporting application.
1.Create a Data Model by importing several related tables.
2.Click Power Pivot > Manage to open the Power Pivot window.
3.Select a table and apply optimizations:
a.Click Advanced > Default Field Set. Choose the fields that should appear automatically on a Power View report when you click on the parent table. See Configure Default Field Set for Power View Reports for details.
b.Click Advanced > Table Behavior. Optimize for report layouts that group data. Grouping is subject to default behaviors that sometimes produced unintended results, such as consolidating rows that should be listed separately. See Configure Table Behavior Properties for Power View Reports for details.
c.Click Advanced > Data Category. Some report visualizations are specific to types of data. For example, if you have a time or date based table, you can assign a Date category that helps Power View with time-based visualizations.
4.Repeat for other tables.
5.In Excel, click Insert > Power View to start a new report. See Power View: Explore, visualize, and present your data for more information.

Tutorial: PivotTable data analysis using a Data Model in Excel 2013

In less than an hour, you can build a PivotTable report in Excel that combines data from multiple tables.  The first part of this tutorial steps you through data import and exploration. In the second half, you’ll use the Power Pivot add-in to refine the data model that lives behind the report, learning how to add calculations, hierarchies, and optimizations for Power View reporting.

After adding these tables, you will now see ThisWorkbookDataModel, which can be now be used to create our PivotTable! Go to the Insert tab, and choose PivotTable. Then choose the option ‘Use an external data source’ which allows you to choose our Data Model as the connection:

When we add information from more than one table, Excel will prompt us to create a relationship. If I want to see the Employee Expenses by Employee Level, I will need to create a relationship between the Employee Type found in both of the tables.

In less than an hour, you can build a PivotTable report in Excel that combines data from multiple tables.  The first part of this tutorial steps you through data import and exploration. In the second half, you’ll use the Power Pivot add-in to refine the data model that lives behind the report, learning how to add calculations, hierarchies, and optimizations for Power View reporting.


SQLBI – Marco Russo : Solving security issue in PowerPivot for SharePoint and Power View May 22, 2013

Filed under: Active Directory,PowerView — sladescross @ 1:25 pm


PowerPivot and PowerView (SSRS) Jumpoff May 15, 2013

Filed under: Data Source,Excel,Jumpoff,PowerPivot,PowerView,Shared Data Source — sladescross @ 12:06 pm

Tutorial list for SQL Server 2012.

Details amongst other things how to create a shared data source for PowerView pointing to the PowerPivot data source stored in an Excel spreadsheet.

Before you can start the tutorial:

  • Save the HelloWorldPicnicModelPowerPivotTutorialRTM.xlsx file to a SharePoint document library or PowerPivot Gallery.
    • If you save it in a SharePoint document library, you create a shared data source that points to the HelloWorldPicnicModelPowerPivotTutorialRTM.xlsx file that you saved in the SharePoint document library.
    • If you save it to a PowerPivot Gallery, it doesn’t need the shared data source. You can open Power View directly from the gallery.
  • Save the images to the associated SharePoint document library. See more information about the Images for Power View and PowerPivot HelloWorldPicnic Samples

The above creates a PowerView report in Excel using a PowerPivot data model.

To do this tutorial, you need to:

The above link is about PowerPivot for Excel.

When you install the add-in, you get the following benefits:

  • A separate application workspace used for importing, relating, enriching, and cleansing data. The workspace opens over Excel, but stores the data in the same .xlsx file that Excel uses. Within the workspace, you can build an analytical database inside Excel when you import and relate data.
  • DAX expression language supports data manipulation and business logic. DAX lets you create formulas in the data layer. Expressions can reference any related table or column. You can use expressions to create calculated columns or measures, reformat data, and group data.
  • Data processing is through a local Analysis Services xVelocity in-memory analytics engine (VertiPaq) that compresses and loads data and makes it available to data visualization objects, such as PivotTables, in a worksheet. The engine runs in the Excel process. There are no administration or configuration tasks to perform. The engine is an internal component of the PowerPivot add-in to Excel.
  • A PowerPivot menu is added to the Excel ribbon so that you can work with data in the Excel workspace.
  • Data access is enabled through updated versions of AMO, ADOMD.NET, and the Analysis Services OLE DB provider. These providers are installed with the add-in and support connections to PowerPivot data.
  • A data feed provider for importing and refreshing data in the OData format.

To use the data interactively, you must either open it in Excel on a local computer that also has PowerPivot for Excel add-in, or you can access it remotely on a SharePoint server that has Excel Services and PowerPivot for SharePoint, or Reporting Services.

PowerPivot for Excel Installation.

You must have Excel 2010 and Office Shared Features installed on your workstation. For more information, see PowerPivot client application requirements in Hardware and Software Requirements (PowerPivot for SharePoint and Reporting Services in SharePoint Mode).

You must have Microsoft NET Framework 4.0 ( or, on Windows 8 Microsoft .NET Framework 4.5 (

You must have Microsoft Visual Studio 2010 Tools for Office Runtime (

If possible, start with a 64-bit Windows operating system that has a large amount of RAM. If you start with a 64-bit computer, be sure to install the 64-bit versions of Office 2010 and PowerPivot for Excel.

If you are installing Excel and PowerPivot for Excel on a Windows server operating system, add the Desktop Experience feature. A reboot is required after you add this feature.


Tabular Data Model Tutorial May 12, 2013

This tutorial is based on Adventure Works Cycles, a fictitious company. Adventure Works Cycles is a large, multinational manufacturing company that produces and distributes metal and composite bicycles to commercial markets in North America, Europe, and Asia. The headquarters for Adventure Works Cycles is in Bothell, Washington, where the company employs 500 workers. Additionally, Adventure Works Cycles employs several regional sales teams throughout its market base.

For the AdventureWorksDW2012 Data File

Attach AdventureWorksDW2012 and set permissions.

In this lesson, in the tabular model designer in SQL Server Data Tools, you will set reporting properties for the Adventure Works Internet Sales tabular model project. Reporting properties make it easier for end-users to select and display model data in Power View. You will also set properties to hide certain columns and tables, and create new data for use in charts.

After completing this lesson and re-deploying the model to a Analysis Services instance integrated with SharePoint and Reporting Services, you can create a data source, specify the data connection information, launch Power View, and design reports against the model.

This lesson does not describe how to create and use Power View reports. This lesson is meant to provide tabular model authors an introduction to those properties and settings that affect how model data will appear in Power View. To learn more about creating Power View reports, see Power View Overview.

You can create a connection string to an Analysis Services data model in multiple ways. How you connect to a data model depends on how it is published or deployed:

  • Published in a PowerPivot workbook in the PowerPivot Gallery on a SharePoint site that is integrated with SQL Server 2012 Analysis Services (SSAS) and SQL Server 2012 Reporting Services (SSRS). The following example shows a connection string:
    Data Source=http://<SharePointSite>/PowerPivot%20Gallery/MyPowerPivotModel.xlsx
  • Deployed to an Analysis Services instance on a server. The following example shows a connection string:
    Data Source=AnalysisServicesInstance; Initial Catalog=Tabular Model Name

After you build a tabular model and deploy it to an Analysis Services tabular mode server, you need to set permissions that make it available to client applications. This topic explains how to permissions and how to connect to a database from client applications.

Client libraries that provide access to Analysis Services databases can be used to connect to model databases that run on a tabular mode server. Libraries include the Analysis Services OLE DB provider, ADOMD.NET, and AMO.

Excel uses the OLE DB provider. If you have either MSOLAP.4 from SQL Server 2008 R2 (file name msolap100.dll, version 10.50.1600.1), or MSOLAP.5 (filename msolap110.dll) that is installed with the SQL Server 2012 version of PowerPivot for Excel, you have a version that will connect to tabular databases. Use the instructions provided in the following topic to check the version of the MSOLAP data provider on your computer: Upgrade PowerPivot for Excel and PowerPivot Data.

Choose from the following approaches to connect to model databases from Excel:

Create a data connection from within Excel, using the instructions provided in the next section.

Create a BI semantic model connection (.bism) file in SharePoint that provides redirection to a database running on an Analysis Services tabular mode server. A BI semantic model connection file provides a right-click command that launches Excel using the model database that you specified in the connection. It will also launch Power View if Reporting Services is installed. For more information about creating and using BI semantic model connection files, see Create a BI Semantic Model Connection to a Tabular Model Database.

Create a Reporting Services shared data source that references a tabular database as the data source. You can create the shared data source in SharePoint and use it to launch Power View. For more information, see Create a Shared Data Source for a Data Model (SSRS).

If you are using SharePoint Server 2010 and PowerPivot for SharePoint, you can create a BI semantic model connection file in SharePoint that provides redirection to a database running on an Analysis Services tabular mode server. A BI semantic model connection provides an HTTP endpoint to a database. It also simplifies tabular model access for knowledge workers who routinely use documents on a SharePoint site. Knowledge workers only need to know the location of the BI semantic model connection file or its URL to access tabular model databases. Details about server location or database name are encapsulated in the BI semantic model connection. For more information about creating and using BI semantic model connection files, see PowerPivot BI Semantic Model Connection (.bism) and Create a BI Semantic Model Connection to a Tabular Model Database.

A BI semantic model connection points to tabular model data. There are two sources for this data:

A tabular model database running on a standalone Analysis Services instance in tabular server mode. A deployment of a standalone Analysis Services instance is external to the farm. Accessing data sources off the farm requires additional permissions, which you can read about in this topic: Create a BI Semantic Model Connection to a Tabular Model Database.

PowerPivot workbooks saved to SharePoint. Embedded PowerPivot databases inside Excel workbooks are equivalent to tabular model databases that run on a standalone Analysis Services tabular mode server. If you already use PowerPivot for Excel and PowerPivot for SharePoint, you can define a BI semantic model connection that points to PowerPivot workbooks in a SharePoint library and build Power View reports using existing PowerPivot data. You can use workbooks created in either SQL Server 2008 R2 or SQL Server 2012 versions of PowerPivot for Excel.

Connecting from Power View to tabular data on a network

When a SharePoint user clicks on a BI semantic connection in a document library, Power View (if it is installed), starts immediately and opens a connection to the tabular model database.

Connections between Power View and a tabular model database follow a double-hop authentication sequence where the user identity is flowed from the client to SharePoint, and then from SharePoint to a back-end Analysis Services tabular model database that runs outside of the farm. The ADOMD.NET client library that handles the connection request always tries Kerberos on the first attempt. If Kerberos is configured, the user identity is impersonated on the connection to the tabular model database, and the connection succeeds.

If Kerberos is not configured and the request fails, Reporting Services makes a second attempt. Under this scenario, the client library connects to Analysis Services using the Reporting Services service identity and NTLM authentication. The identity of the Power View user is passed on the connection string using the effectiveusername parameter.

Only a member of the system administrator role on the Analysis Services instance has permission to make a connection using the effectiveusername parameter and impersonate another user on the server instance. For this reason, the execution account of the Reporting Services shared service must have administrative rights on the Analysis Services instance.  Instructions for granting administrative permissions to the service account is provided in this topic, Create a BI Semantic Model Connection to a Tabular Model Database.

The following illustration shows a connection sequence that uses the same Windows user identity for each connection. On the last connection to Analysis Services, the connection is made by the Reporting Services service application identity, passing the Windows user identity using effectiveusername.

Create and Manage Shared Data Sources (Reporting Services in SharePoint Integrated Mode)

Redeploy the Adventure Works Internet Sales tabular model

Because you have changed the model, you must re-deploy it. You will essentially repeat the tasks performed in [[Lesson 14: Deploy]].

To redeploy the Adventure Works Internet Sales tabular model

  • In SQL Server Data Tools, click the Build menu, and then click Deploy Adventure Works Internet Sales Model.

    The Deploy dialog box appears and displays the deployment status of the metadata as well as each table included in the model.

Next Steps

You can now use Power View to visualize data from the model. Ensure the Analysis Services and Reporting Services accounts on the SharePoint site have read permissions to the Analysis Services instance where you deployed your model.

To create a Reporting Services report data source that points to your model, see Table Model Connection Type (SSRS)


Excel 2013 PowerPivot and PowerView April 17, 2013

Filed under: Excel 2013,PowerPivot,PowerView — sladescross @ 10:36 pm

What’s new in Power View in Excel 2013 and in SharePoint Server

1.In Power View in the Field List, click the arrow next to the KPI.

It expands to show the fields in the KPI:
Value : Also called the base value, the calculated field that represents the current value for the item in that row of the table or matrix.
Goal: Also called the target value, the value against which the current value is evaluated. This could be a fixed number, some goal all the rows should achieve, or a calculated field, which might have a different goal for each row.
Status: The visual indicator of the value. In Power View in Excel, you can edit the KPI, choosing which indicators to use and what values to trigger each indicator.

Create a KPI in Power View in Excel

KPIs are based on explicit calculated fields in the data model. In the Power View Field List, calculated fields have a calculator icon next to them. If the data model contains calculated fields, then you can actually create KPIs in Power View in Excel. You create them in Power View in Excel, or by managing the Data Model in the PowerPivot window. Then you can add the KPIs you create to your Power View report.



Reporting Services for SharePoint Installation November 4, 2012

Filed under: Installation,PowerView,Reporting Services — sladescross @ 11:32 pm

Installing Reporting Services SharePoint Mode Report Server for Power View and Data Alerting

The Microsoft SQL Server Reporting Services add-in for SharePoint 2010 products.

The add-in installs the Reporting Services user interface (UI) pages and features on a SharePoint web front-end server. The UI features include Power View, administration pages in SharePoint Central Administration, feature pages used within SharePoint document libraries, and Reporting Services Data Alerting pages.

The Microsoft SQL Server Reporting Services report server installed in SharePoint Mode

The report server handles the data and report processing and rendering as well subscription and Data Alert processing. The SharePoint mode report server is architected and installed as a SharePoint Shared Service.

The following steps assume that an administrator is installing and configuring the server. The Setup user in SharePoint is also a farm administrator and often the primary site administrator for the default site collection. If you are dividing the following steps among several people, additional permissions might be required in order for the following steps to work.

Run the SharePoint 2010 Products Preparation Tool

You must have the SharePoint 2010 installation media. The preparation tool is PrerequisiteInstaller.exe on the installation media.

Install SharePoint Server 2010 enterprise or enterprise evaluation edition.

When installing SharePoint, you can choose to configure the farm later by not running the SharePoint 2010 Product Configuration Wizard after Setup is finished. Waiting to configure the farm will allow you to use a SQL Server 2012 Database Engine instance, which is installed in a later step, as the farm’s database server. To configure the farm, you will use the PowerPivot Configuration Tool. It includes actions for provisioning the farm if the farm is not yet configured.

Install SharePoint Server 2010 SP1.

Download SP1 from

Run SQL Server 2012 Setup to install the Database Engine and PowerPivot for SharePoint.

Install PowerPivot for SharePoint

Step 1 explains how to install PowerPivot for SharePoint. In this step, be sure to click the checkbox on the Setup Role page that adds the Database Engine to the role. Doing so adds the Database Engine to your installation so that you can use it as the farm’s database server when you configure the farm in the next step. However, if the farm is already configured, you can skip this step.

Step 2 asks you to configure the server. For this step, choose the PowerPivot Configuration tool. Although several approaches are available, using the configuration tool is the most efficient approach for a standalone installation.

If SharePoint 2010 is installed but not configured, the tool pre-selects actions that will create the farm, a default web application, and a root site collection. Be sure to leave these options selected so that the farm will be created. If you already configured the farm, the tool will omit these actions, and offer just the actions that are necessary for configuring PowerPivot for SharePoint.

Step 3 instructs you to install the SQL Server 2008 R2 version of the Analysis Services OLE DB Provider. This step is important for supporting versions of a workbook that were created in the 2008 R2 version of PowerPivot for Excel.

Verify the farm is operational.

First, start Central Administration and confirm that it is available. Next, open the team site by entering http://localhost. You should see a SharePoint team site.

Verify that PowerPivot for SharePoint is operational.

Verify a PowerPivot for SharePoint Installation

This task confirms PowerPivot data access using a sample workbook that you upload.

Run SQL Server 2012 Setup to install and configure Reporting Services and the Reporting Services Add-in.

Install Reporting Services SharePoint Mode as a Single Server Farm

Optionally, while installing Reporting Services, you can add an additional Analysis Services instance to the Setup feature tree if you want a second resource for hosting tabular data. The additional Analysis Services instance would be used to host tabular model databases that you create in SQL Server Data Tools (SSDT). Tabular databases are a valid data source for Power View reports.

Install Analysis Services in Tabular Mode

Verify that Reporting Services is operational.

Verify a Reporting Services Installation

(Site Administrators) Configure SharePoint permissions.

Contribute permissions are required to add, edit, or delete items in SharePoint libraries. View permission level is sufficient for read-only access to reports and PowerPivot workbooks that present embedded data.

PowerPivot workbooks that are accessed as external data sources (where the workbook URL is a connection string in another workbook or report) require Read permissions, which is higher than View permissions.

BI semantic model connections also required Read permissions. You might need to create new permission levels or SharePoint groups to get the correct permissions in place.

(Site Administrators) Extend document libraries

Extend document libraries to use BI content types: BI semantic model connections, Reporting Services Shared Data Sources, Report Builder reports:
Enable content type management. In Shared Documents or another document library, in the Library tab, click Library Settings. Under General Settings click Advanced settings. In Content Types, select Yes to allow management of content types, and then click OK.

Select the BI content types. In the Library tab, click Library Settings. Under Content Types, click Add from existing site content types. From the Business Intelligence content type group, add BI Semantic Model Connection File and Report Data Source. Optionally, you can also add other Reporting Services content types, such as Report Model, to enable additional report building scenarios.

For more information, see Add a BI Semantic Model Connection Content Type to a Library (PowerPivot for SharePoint) and Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode).

(Site Administrators) Create data connection files that are used to launch Power View.

You must create a BI semantic model connection (.bism) or a Reporting Services shared data source (.rsds) as a data source for Power View. After you create a data connection file, you can launch Power View using the data connection as its data source.

Create a BI Semantic Model Connection to a PowerPivot Workbook

Create a BI Semantic Model Connection to a Tabular Model Database

Create a Shared Data Source for a Data Model (SSRS)

Note: Power View is available because you installed the SQL Server 2012 version of Reporting Services and configured the server as a shared service. If you installed Reporting Services and configured it for the SQL Server 2008 level of integration, Power View is not available.

The diagram shows a typical three tier environment and the numbered items in the diagram are described in the following list:

(1) Multiple web front-end (WFE) servers. The WFE servers require the Reporting Services add-in for SharePoint 2010. The following steps add a second application server to this tier.

(2) Two application servers running Reporting Services and web sites, for example Central Administration.

(3) Two SQL Server database servers.

(4) Represents a software or hardware network load balancing solution (NLB)

Verify the server was added to the SharePoint farm.

Install the SQL Server 2012 Reporting Services add-in for SharePoint 2010 products.

Create or identify the accounts used in a report server deployment. You must have a service account for the Report Server service, and credentials for connecting to the report server database

Decide on an instance of SQL Server to host the report server database. You can use a local or remote instance of SQL Server. You should choose an instance that is on a computer that has the storage capacity to accommodate your reports.

4.Start the SharePoint ‘Claims to Windows Token Service’: Start the Claims to Windows Token Service through SharePoint Central Administration on the Manage Services on Server page. The service should be started on the server that will be performing the action. For example if you have a server that is a WFE and another server that is an Application Server that has the Reporting Services shared service running, you only need to start C2WTS on the Application Server. C2WTS is not needed on the WFE.

Installation and initial configuration

Install the SharePoint add-in on all Web front-end (WFE) computers.

Add an Additional Reporting Services Web Front-end to a Farm

Install SQL Server SQL Server 2012 Reporting Services and the Database engine.

Install Reporting Services SharePoint Mode as a Single Server Farm

Create at least one SSRS service application and configure service app association.

See the ‘Service Application’ section in Install Reporting Services SharePoint Mode as a Single Server Farm

Additional Configuration

Add SSRS content types to your document library.

Add Report Server Content Types to a Library (Reporting Services in SharePoint Integrated Mode)

Provision SQL Server Agent

Provision Subscriptions and Alerts for SSRS Service Applications

Configure e-mail settings for your Service application

Configure E-mail for a Reporting Services Service Application

Configure Claims to Windows Token Service (c2WTS)
Claims to Windows Token Service (C2WTS)

Reporting Services can be installed from the command line using the input settings for the SQL Server setup program.

setup.exe /q /ACTION=”Install” /IACCEPTSQLSERVERLICENSETERMS /FEATURES=”RS_SHP” /INSTANCEDIR=”C:\Program Files\Microsoft SQL Server” /INSTALLSHAREDDIR=”C:\Program Files\Microsoft SQL Server” /INSTALLSHAREDWOWDIR=”C:\Program Files (x86)\Microsoft SQL Server” /INSTALLSQLDATADIR=”C:\Program Files\Microsoft SQL Server” /SECURITYMODE=”SQL” /SAPWD=”*****” /PID=”[Your PID Value]” /SQLSYSADMINACCOUNTS=”[Account Name]” “AutoSql Admin Group” /ASSYSADMINACCOUNTS=”[Account Name]” /UPDATEENABLED=”False”

A distributed server deployment uses multiple computers, where each computer hosts a single server component. You might use this deployment configuration if you want better performance for processing complex reports or large datasets for a small organization or workgroup.

Three-Computer Deployment

The following illustration shows components for a three-computer deployment.

The first computer hosts an instance of a SharePoint product or technology. The second computer hosts SQL Server Reporting Services. The third computer hosts an instance of the Database Engine.

In the illustration, notice that the Database Engine does not require a local installation of a report server or an instance of a SharePoint product or technology.

To use a remote database server with a deployment of a SharePoint product or technology, choose the Advanced installation option when installing an instance of a SharePoint product or technology, or use Central Administration to modify the database server setting. To select a remote database server for Reporting Services, use the Reporting Services Configuration tool. For more information about edition and connection requirements for a report server database, see Creating a Report Server Database and How to: Create a Report Server Database for SharePoint Integrated Mode (Reporting Services Configuration).



BIS SharePoint Installation Extras November 1, 2012

Filed under: Disk Space Usage,PowerPivot,PowerView,Reporting Services — sladescross @ 1:29 pm

PowerPivot configure disk space usage.

In Central Administration, in Application Management, click Manage Services on Server.

  • Click SQL Server Analysis Services.Notice that limits are set on the Analysis Services instance that runs on the physical server, and not at the service application level. All service applications that use the local Analysis Services instance are subject to the single maximum disk space limit that is set for that instance.
  • In Disk Usage, set a value (in gigabytes) for Total disk space to set an upper limit on the amount of space used for caching purposes. The default is 0, which allows Analysis Services to use all available disk space.
  • In Disk Usage, in the Delete cached databases in last ‘n’ hours setting, specify last-used criteria for emptying the cache when disk space is at the maximum limit.The default is 4 hours, meaning that all databases that have been inactive for 4 hours or more are deleted from the file system. Databases that are inactive but still in memory are unloaded and then deleted from the file system.

A PowerPivot for SharePoint installation includes two services that support server operations. The SQL Server Analysis Services (PowerPivot) service is a Windows service that provides PowerPivot data processing and query support on an application server. The login account for this service is always specified during SQL Server Setup when you install Analysis Services in SharePoint integrated mode.

PowerPivot integration with Reporting Services.

You can build Reporting Services reports as a way to visualize PowerPivot data. Reporting Services offers rich data visualization through charts and maps, additional rendering formats, and comprehensive subscription and delivery options.

Use Report Designer with PowerPivot data source.

PowerView reporting.

Components of PowerPivot for SharePoint.


PowerView October 21, 2012

Filed under: PowerView,PowerView Wiki — sladescross @ 9:20 pm

PowerView Wiki Jump Off



BIS PowerView Installation October 6, 2012

Filed under: BIS,Installation,PowerView — sladescross @ 1:25 pm

PowerView Installation of SQL Server BIS components.

Summary: This document contains step-by-step instructions for installing and testing the Microsoft Business Intelligence infrastructure based on SQL Server 2012 and SharePoint 2010, focused on SQL Server 2012 Reporting Services with Power View. This document describes how to completely install the following scenarios: a standalone instance of SharePoint and Power View with all required components; a new SharePoint farm with the Power View infrastructure; a server with the Power View infrastructure joined to an existing SharePoint farm; installation on a separate computer of client tools; installation of a tabular instance of Analysis Services on a separate instance; and configuration of single sign-on access for double-hop scenarios with and without Kerberos. Scripts are provided for all/most scenarios.



Get every new post delivered to your Inbox.

Join 63 other followers