Database Reference
In-Depth Information
Earliest Start Time: The Earliest Start Time specifies the time of day to run the refresh
process.
E-mail Notifications: The E-mail Notifications setting lets you specify who should receive an
e-mail from SharePoint each time the scheduled refresh is run. Note that individuals speci-
fied will receive an e-mail whether the process ran with errors or ran successfully.
Credentials: Most data sources require authentication in order to pull data in a refresh pro-
cess. The Credentials setting specifies how authentication is passed to external data sources.
There are three options:
Use the Data Refresh Account Configured by the Administrator: This means that a SharePoint
system account authenticates to the data source. You typically have to work with your
SharePoint administrator to set up this authentication method and ensure that the data
source can use SharePoint's system account.
Connect Using the Following Windows User Credentials: This enables you to enter a user-
name and password for authentication. It's not a good idea to use your own personal
username and password here. Instead, this option is best used with an application
account — a dummy account created by your database administrators.
Connect Using the Credentials Saved in Secure Store Service (SSS) to Log On to the Data
Source: This option allows you to refresh data connections without a password. To do so,
you need to acquire a Secure Store ID from your SharePoint administrator.
Data Sources: This setting lets you define whether all data connections are refreshed, or only
specific connections. Deselect the All Data Sources check box to enable the selection of indi-
vidual connections in your workbook.
Managing Power Pivot Performance
When you publish Power Pivot reports to the Web, you want to give your audience the best experi-
ence possible. A large part of that experience is ensuring that performance is not an issue. In terms of
applications and reporting, performance is typically synonymous with speed. Speed is how quickly
your application performs certain actions, such as opening within the browser, running queries, and
filtering.
Because Power Pivot inherently paves the way for large amounts of data with fairly liberal restrictions,
it's common to end up with BI solutions that work, but are unbearably slow. And nothing turns your
intended audience away from your slick new BI solution faster than sluggish performance.
To help you create the best interactive experience for your users, and ultimately improve user adop-
tion of your published BI solutions, we wrap up this chapter with some best practices for optimizing
the performance of your Power Pivot reports.
 
Search WWH ::




Custom Search