سوال در زمينه report maneger [بایگانی]

hanann

پنج شنبه 13 فروردین 1388, 16:00 عصر

Reviewing Execution Properties

Execution properties are a subset of the report properties maintained for each report. When you understand the implications of the execution property settings, you can choose the most appropriate property setting for your reporting environment. Execution properties allow you to manage reports by balancing system resources and performance with the users’ information requirements. For example, you set up caching to achieve a reasonable balance when data used in the report is not changing rapidly at the source. To use caching, you first need to change the data sources properties so you can assign logon credentials that will be used to execute the report for the cache. Separate logon credentials are required by Reporting Services

to implement report caching in order to make a single report available to many users.

In this procedure, you’ll open the Execution Properties page for your report to review the

available options.

Open the report’s Execution Properties page

1. Click the Sales Summary link.

Assume for a moment that you’ve just started a new browser session. Just like the previ-

ous time you opened this report, a message is displayed to let you know that several

activities are occurring: “Report is being generated”. Each time a report executes on

demand, as you initiated in this step, a query is executed to retrieve data from the

rs2005sbsDW database. The data is processed with the report, which is then rendered

into the HTML display in your browser window.

2. Click the Properties tab.

3. Click the Execution link in the left frame of the page.

Notice that you can render the report either on demand or on a scheduled basis. When

rendered on demand, the report typically displays the most recent data and may or may

not use caching. By default, a report renders on demand without caching. When ren-

dered on a scheduled basis, the report is stored as an execution snapshot, which cap-

tures data for the report at a point in time.

Execution properties control when report processing occurs. When a report executes on

demand, which occurs every time another user opens the report, the defined query runs

and the query results are merged with the report definition to produce the HTML out-

put format. You can alternatively set the execution properties to process the report at a

scheduled time so the report is ready when accessed. However, if you choose to do this,

let users know that the data in the report is not current. Another option is to cache a

report temporarily to make the same output available to several users for the duration of

a specified timeframe. The key difference between a snapshot and a cached report is that

the snapshot is stored permanently until physically deleted, while the cache is stored

temporarily with a predetermined expiration.

Changing Data Sources Properties

Data sources properties define the connection to be used for query execution. You can change these properties to override the credentials used for authentication when the report executes. Queries that run unattended, such as when a report is cached or scheduled for execution, require stored credentials. These credentials are encrypted when stored in the ReportServer database.

for your report, you need to change the credentials information in the data sources properties.

Use secured credentials

1. Click the Data Sources link in the left frame of the page.

2. Click the Credentials Stored Securely In The Report Server option.

3. Type ReportExecution as the user name.

This SQL Server login was added when you installed the sample databases.

4. Type ReportExecution as the password.

Important In a production environment in which you are using stored credentials, it’s

important to test the report by viewing it to ensure that you have entered the user name

and password correctly. The credentials will not be validated until the report executes.

5. Click Apply.

Changing Execution Properties

You might want to temporarily cache a report to improve performance. When a user first

opens the report, a copy of the report is placed in temporary storage and made available to other users who open the same report. You can also assign a time limit for the cache so that the report can be periodically refreshed with more current data.

Note The type of caching discussed in this chapter refers to the access of a single report by multiple users. When you open a report, the report is automatically cached for you as part of your browser session. You can then return to this report repeatedly during the same session without having to wait for the query to execute again, regardless of the current setting of the report’s execution properties. When you close the browser window, the report is removed from this cache.

In this procedure, you’ll change the report execution properties to cache your report, and set the cache to expire after 60 minutes.Define a report cache

1. Click the Execution link.

2. Click the Cache A Temporary Copy Of The Report. Expire Copy Of Report After A Num-ber Of Minutes option to cache the report and expire after a specified number of min-utes. Change the number of minutes to 60.

3. Click Apply at the bottom of the page.

The next time this report is opened, a temporary copy of it will be placed in the cache to

speed up its display for any later requests by other users within the same hour. At the

end of 60 minutes, the temporary copy is removed from the cache. A new copy is only

placed in the cache when a user requests the report again.

As mentioned earlier, by using the caching option, you can improve performance for

the next user who opens the same report. Any subsequent request for a report results

in the display of the cached copy of the report rather than in the execution of the

query and processing of the report. That is, any subsequent request displays the

cached report until the cache expires. The purpose of expiring the cache on a periodic

basis is to force the report to be refreshed with the most current data when the next

user accesses the report. The result is a new cached instance of the report until the

next scheduled expiration

فایل اپلود نمیشد برای همین متن را اینجا کپی کردم .