Export (0) Print
Expand All

Deploying Reporting Services in a Global Environment

SQL Server 2000

Reporting Services includes localized language resources for Setup, Report Designer, Report Manager, HTML Viewer, and all messages that are returned from a report server. Reporting Services is localized into all languages supported by SQL Server. The resources for all supported languages are installed during Setup. You do not need to run a separate installation program to add support for additional languages.

For server-side components such as Report Manager and HTML Viewer, the language resource that is in effect for any given user is determined at run time. Both the client application (usually a browser) and the operating system of the computer running the report server play a part in determining which language resource is used. This topic explains how the browser and operating system locale settings affect language resource selection at run time.

In addition to the localization issues discussed above, this topic also provides information about report language settings, explains which items are not localized, and describes the effect of time zones and clock settings on a report server and reports.

Language Settings for Reports and Report Designer

In Report Designer, you can set the language on a report to show the formatted values (such as dates, currency, and numbers) of a specific language. Setting the language on a report is recommended if you deploy the report in a multilingual environment. If you do not set a language, the client application determines the formats that are used. Different client locales will show different formatting on the same report, which may be confusing to users who do not understand the effect that language settings have on a report. For more information, see Localizing Reports.

For Report Designer itself, the language resource that is applied to the report-authoring environment is the same as the language version used for Visual Studio. For example, if you are running a Japanese version of Visual Studio, the Japanese language resource for Report Designer is used. If you are running a language version of Visual Studio that is not supported by Reporting Services, the neutral resource language is used instead. For more information about neutral resources, see "Operating System Language Settings" later in this topic. For more information about neutral resources in general, see Microsoft Visual Studio .NET product documentation.

Browser Language Settings

The browser language setting is the primary factor in determining which language resource is used by the report server for that client connection. For example, a user who accesses a Japanese report server using a French version of Internet Explorer will work with French versions of Report Manager, HTML Viewer, and the report server folder namespace. In addition, all errors, warnings, and informational messages will be returned in French.

Note that only the user interface components are affected by client language settings. The reports that you view and manage retain the language settings that were previously set for the report. In a multilingual environment, these factors may combine in such a way that multiple languages are displayed to a user within the same browser page. For example, if you use a French client to access a Japanese report, both French and Japanese characters are displayed to the user in the following ways:

  • Report Manager and the report toolbar will be in French because the client application is in French.
  • The report will be in Japanese (as will any report history snapshots of the report, parameter properties, or subscription properties that are set for the report) because the report language property is set to Japanese.

Operating System Language Settings

The language of the operating system determines the neutral resource that is used if a match cannot be found between a client application and a Reporting Services language. If a client application connects to a report server in an unsupported language, the neutral resources are returned to the application.

A few items are always articulated in the language that corresponds to the operating system language setting, regardless of client application locale. The following table describes these items.

Item Description
Predefined roles Reporting Services installs with several predefined roles (Browser, Publisher, Content Manager, My Reports, System Administrator, and System User) that are articulated in the language resource of the operating system that runs the report server.
Users folder, and My Reports folder These folder names are reserved when the My Reports feature is enabled. This feature requires a fixed folder structure. Because the report server manages reserved names, reserved folder names are articulated in the language resource of the operating system that runs the report server.

Nonlocalized Items

Reporting Services does not include multilanguage support for log files, the AdventureWorks sample database, sample reports, and sample applications. These items are available only in English.

Time Zones and Clock Settings

A report server always uses the local time of the computer on which it is installed. You cannot configure it to use a different time zone. If a client application points to a report server in a different time zone, the report server time zone is used to execute a scheduled operation. In Report Manager, the time zone is indicated on each scheduling page so that you know exactly when a scheduled operation will occur.

Changing the Time Zone

If you change the time zone on a computer hosting a report server, you must restart Internet Information Services (IIS) in order for the time zone change to take effect.

Timestamp values of existing generated reports (for example, report history snapshots) are synchronized to the new time zone setting. If you generated a report history snapshot at 9:00 A.M., and then reset the time zone ahead one time zone, the timestamp on the generated snapshot will change from 9:00 A.M. to 10:00 A.M.

Schedules retain existing settings, except that they are mapped to the new time zone. For example, if a schedule runs at 2:00 A.M. Pacific Standard Time and you change the time zone to East Australia Standard Time, the schedule runs at 2:00 A.M. East Australia Standard Time.

Property timestamp values (for example, the time at which a folder or linked report item is created) are not synchronized to a new time zone setting. If you create an item on June 25 at 9:00 A.M., and then reset the time zone or clock, the timestamp remains June 25 at 9:00 A.M.

Changing the Clock Settings

Changing the computer clock has no effect on existing timestamp values (for example, if you move the clock forward an hour, the timestamps of report history snapshots do not change). There may be a delay of 10 seconds before the Scheduling and Delivery Processor uses the new setting. The actual delay may vary if you modified polling interval settings in the configuration files.

See Also

Deploying and Administering Reporting Services Components

Deployment and Administration Tools

Securing Reports for Global Access

Show:
© 2014 Microsoft