Archive for December 2010

Linked dimensions

By on December 31, 2010
This entry is filed under Uncategorized.

A linked dimension in Microsoft SQL Server Analysis Services (SSAS) is based on dimension that is stored in another database of the Analysis Services. The source database for a linked dimension can be on a different server or on the same server. With the help of a linked dimension it is possible to create, maintain, and store a dimension on one Analysis Service database, and also make that dimension available to users of multiple databases. To users, a linked dimension appears like any other dimension.

Share

XMLA

By on December 30, 2010
This entry is filed under SQL Server, SQL Server Business Intelligence and tagged .

Microsoft SQL Server Analysis Services uses the XML for Analysis (XMLA) protocol to handle all communications between client applications. It also includes Business Intelligence Development Studio (BIDS), an instance of Analysis Services, and SQL Server Management Studio (SSMS). XMLA defines two accessible methods to support the manipulation and discovery of data in both tabular and multidimensional formats. These two methods are Discover and Execute, which handle incoming and outgoing information in XML format. XMLA also defines a collection of XML elements and data types.

Share

Dimension Processing Destination

By on December 29, 2010
This entry is filed under SQL Server, SQL Server Business Intelligence and tagged .

The Dimension Processing destination is used to load and process an SQL Server 2005/2008 Analysis Services (SSAS) dimension. Following features are included in the Dimension Processing destination:
Options to perform full, incremental, or update processing
Error configuration to specify whether dimension processing stops after a specified number of errors or simply ignores errors
Mapping of input columns to columns in the dimension tables
An Analysis Services connection manager is used by the Dimension Processing destination to connect to the Analysis Services project or the instance of Analysis Services that contains dimensions processed by the destination. The Dimension Processing destination has one input and does not support an error output.

Share

Translations

By on December 28, 2010
This entry is filed under SQL Server, SQL Server Business Intelligence and tagged .

Translations are used in Microsoft SQL Server Analysis Services (SSAS) to support multiple languages. A translation contains a language identifier and bindings for properties of Analysis Services objects, which can be presented in different languages. For example, it is possible to define a translation for an Analysis Services database to present the description and caption of that database in a specified language.

Share

Partition Processing destination

By on December 27, 2010
This entry is filed under SQL Server, SQL Server Business Intelligence and tagged .

The Partition Processing destination is used to load and process a SQL Server Analysis Services partition. An Analysis Services connection manager is used by the destination to connect to the Analysis Services project or the instance of Analysis Services that contains the cubes and partitions the destination processes. This destination does not support an error output and has only one input.

Share

BIDS

By on December 22, 2010
This entry is filed under SQL Server Business Intelligence.

BIDS (Business Intelligence Development Studio) is a development tool used to create reports, packages, and analysis projects. It is a part of Visual Studio 2005. The tool contains projects and wizards to create the reports, packages and analysis projects either automatically or manually.

Share

Drillthrough reports

By on December 21, 2010
This entry is filed under SQL Server Business Intelligence and tagged .

Drillthrough reports are the standard reports that are accessed through a hyperlink on a text box in the original report. Drillthrough reports work with a main report and are the target of a drillthrough action for a report item such as a chart or a placeholder text. The summary information is displayed by the main report, for example in a chart or matrix. Actions that are defined in the chart or matrix provide drillthrough links to reports that display greater details based on the aggregate in the main report. It is possible to filter a drillthrough report with the help of parameters.

Share

URL access option

By on December 18, 2010
This entry is filed under SQL Server Business Intelligence.

URL access is one of the three options for integrating Reporting Services into custom applications. The URL access option is used for integrating report viewing into user’s applications if the ReportViewer controls are not an option. As an example, if a user is developing an application that uses a version of the .NET Framework that shipped prior to Microsoft Visual Studio 2005 or an application developed with unmanaged code, then the user will want to consider URL access for viewing reports. In addition to viewing reports within the user’s application, URL access is helpful for sending links to reports to the users via e-mail.

Share

Core components of the SQL Server Reporting Services

By on December 17, 2010
This entry is filed under SQL Server Business Intelligence and tagged .

The core components of the SQL Server Reporting Services are as follows:

  • A complete tool set that can be used to create, view, and manage reports.
  • An API that allows developers to extend and integrate report and data processing in custom applications, or create custom tools to manage and build reports.
  • A Report Server component that is able to host and process reports in a variety of formats. Output formats include HTML, TIFF, Excel, CSV, PDF, and more.
Share

Report Builder role

By on December 16, 2010
This entry is filed under SQL Server Business Intelligence and tagged .

The Report Builder role is a predefined role, which includes tasks for loading reports in Report Builder as well as navigating and viewing the folder hierarchy. In order to create and modify reports in Report Builder, a user must also have a system role assignment. This system role assignment should include the “Execute report definitions” task that are required for processing reports locally in Report Builder.

Share
Older Entries »